October 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12853) No repository found at http://download.jboss.org/jbosstools/updates/juno/SR1a/

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-12853: ---------------------------------- Summary: No repository found at http://download.jboss.org/jbosstools/updates/juno/SR1a/ Key: JBIDE-12853 URL: https://issues.jboss.org/browse/JBIDE-12853 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite Affects Versions: 4.0.0.Beta1 Reporter: Radim Hopp Assignee: Nick Boldt Priority: Critical Fix For: 4.0.0.Beta1 {code} !ENTRY org.eclipse.equinox.p2.core 4 0 2012-10-15 13:09:18.429 !MESSAGE Provisioning exception !STACK 1 org.eclipse.equinox.p2.core.ProvisionException: No repository found at http://download.jboss.org/jbosstools/updates/juno/SR1a/. at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:393) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:675) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:165) at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:105) at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:758) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:651) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:165) at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:105) at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:758) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:651) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.addRepositories(PrepareInstallProfileJob_e_3_6.java:389) at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.computeInstallableUnits(PrepareInstallProfileJob_e_3_6.java:207) at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.run(PrepareInstallProfileJob_e_3_6.java:95) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) !SUBENTRY 1 org.eclipse.equinox.p2.metadata.repository 4 1000 2012-10-15 13:09:18.432 !MESSAGE No repository found at http://download.jboss.org/jbosstools/updates/juno/SR1a/.{code} I think, this leads to lot of not available connectors. For example, when tryting to install m2e-apt from JBoss Central: {code} !ENTRY org.eclipse.mylyn.discovery.ui 4 0 2012-10-15 13:09:34.900 !MESSAGE Problems occurred while performing installation: The following connectors are not available: Maven Integration for Eclipse JDT APT (m2e-apt) (id=org.jboss.tools.maven.apt.feature.feature.group, site=http://download.jboss.org/jbosstools/updates/development/juno/centra...) !STACK 1 org.eclipse.core.runtime.CoreException: The following connectors are not available: Maven Integration for Eclipse JDT APT (m2e-apt) (id=org.jboss.tools.maven.apt.feature.feature.group, site=http://download.jboss.org/jbosstools/updates/development/juno/centra...) at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.checkForUnavailable(PrepareInstallProfileJob_e_3_6.java:300) at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.computeInstallableUnits(PrepareInstallProfileJob_e_3_6.java:210) at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.run(PrepareInstallProfileJob_e_3_6.java:95) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) !SUBENTRY 1 org.eclipse.mylyn.discovery.ui 4 0 2012-10-15 13:09:34.900 !MESSAGE The following connectors are not available: Maven Integration for Eclipse JDT APT (m2e-apt) (id=org.jboss.tools.maven.apt.feature.feature.group, site=http://download.jboss.org/jbosstools/updates/development/juno/centra...) {code} -- 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, 4 months

3
14
0 / 0

[JBoss JIRA] (JBIDE-12828) migrate JBT & JBDS jobs to use new github repos

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12828: ---------------------------------- Summary: migrate JBT & JBDS jobs to use new github repos Key: JBIDE-12828 URL: https://issues.jboss.org/browse/JBIDE-12828 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng, updatesite Affects Versions: 4.0.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.0.0.CR1 For first the trunk jobs, then AFTER Beta1 is released the stable_branch jobs, the following must be done. Work to start Oct 22 {quote} * [Max] For every repo moved - svn delete in trunk, put Readme with pointer. * [Max] Open branch 4.0.0.Beta1 for writes, keep trunk locked down. * [Nick/Mickael] create root poms for chunk repos * [Nick/Mickael] switch trunk jobs to source from github instead of svn * [Nick] for N:1 "chunk" repos (base, server, javaee, central): merge jbosstools-base/{as,archives,jmx}/site/* into jbosstools-base/site/* - one site w/ all features on it * [Nick/Mickael] Change jbosstools composite http://download.jboss.org/jbosstools/builds/staging/_composite_/core/ sites to point at "server" update site folder instead of as, archives, and jmx when building JBT aggregate site * [Nick] make sure all jobs (including rsync for download.jboss.org) are updated to fetch from git instead of svn * [Nick/Mickael] make sure all refs to promote.sh, jbosstools-cleanup.sh, promote.sh are pointed at github instead of svn * for 1:1 individual repos: no change needed for ./site/ folder {quote} (see also http://ether-man.rhcloud.com/p/build.next ) -- 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, 4 months

1
66
0 / 0

[JBoss JIRA] (JBIDE-11655) Failed while installing JPA 2.0.

by Marius Bogoevici (JIRA)

Marius Bogoevici created JBIDE-11655: ---------------------------------------- Summary: Failed while installing JPA 2.0. Key: JBIDE-11655 URL: https://issues.jboss.org/browse/JBIDE-11655 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Marius Bogoevici java.lang.NullPointerException at org.eclipse.jpt.common.core.internal.resource.ModuleResourceLocator.getDefaultResourceLocation(ModuleResourceLocator.java:34) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.defaultResourceLocation(JpaFacetInstallDelegate.java:141) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createPersistenceXml(JpaFacetInstallDelegate.java:111) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createProjectXml(JpaFacetInstallDelegate.java:101) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.execute_(JpaFacetInstallDelegate.java:62) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetActionDelegate.execute(JpaFacetActionDelegate.java:34) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) at org.jboss.tools.maven.jpa.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:124) at org.jboss.tools.maven.jpa.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:87) at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:302) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:234) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:150) at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$1.doCreateMavenProjects(MavenImportWizard.java:164) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73) at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$3.runInWorkspace(MavenImportWizard.java:249) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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, 4 months

5
15
0 / 0

[JBoss JIRA] (JBIDE-12237) Improve UI of Runtimes dialog

by Lucia Jelinkova (JIRA)

13 years, 4 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-12892) New graphic images for JBoss Tools, JBoss Tools Web, JSF and Struts Wizards

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-12892: ------------------------------------- Summary: New graphic images for JBoss Tools, JBoss Tools Web, JSF and Struts Wizards Key: JBIDE-12892 URL: https://issues.jboss.org/browse/JBIDE-12892 Project: Tools (JBoss Tools) Issue Type: Task Components: common/jst/core, JSF, struts/shale Reporter: Daniel Azarov Assignee: Daniel Azarov We need new graphic images for follow wizards: JBoss Tools: - Create a Sample RESTful Web Service - Create a Sample Web Service - Simple Web Service JBoss Tools Web: - CSS File - JBoss Datasource - Properties File - TLD File - Web Descriptor JSF: - Faces Config - JSF project Struts: - Struts Config - Struts project - Tiles File - Validation File -- 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, 4 months

2
23
0 / 0

[JBoss JIRA] (JBIDE-12890) "Add missing required attribute(s)" quick fix does not work without editor

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-12890: ------------------------------------- Summary: "Add missing required attribute(s)" quick fix does not work without editor Key: JBIDE-12890 URL: https://issues.jboss.org/browse/JBIDE-12890 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 4.0.0.Beta1 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 4.0.0.CR1 -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-12783) Missing QuickFix context menu within Source pane of VPE for JSF project

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-12783: ----------------------------------- Summary: Missing QuickFix context menu within Source pane of VPE for JSF project Key: JBIDE-12783 URL: https://issues.jboss.org/browse/JBIDE-12783 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 4.0.0.Alpha2 Environment: Linux 64bit, JBT 4.0.0.Alpha2-v20121002-1149-B19 Reporter: Vlado Pakan Assignee: Alexey Kazakov Priority: Critical Fix For: 3.3.1 Attachments: disabledquickfixmenuproblemsview.png, noquickfixmenuvpe.png 1. Create JSF project 2. Open inputUserName.jsp 3. Change EL "#{user.name}" to "#{user.sname}" 4. Warning marker is displayed on side of VPE and warning appeared in Problems view 5. Right click on changed EL ERROR: There is no QuickFix context menu !noquickfixmenuvpe.png! ERROR: QuickFix menu in Problems view is disabled !disabledquickfixmenuproblemsview.png! Workaround is to press Ctrl+1 in VPE editor -- 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, 4 months

5
32
0 / 0

[JBoss JIRA] (JBDS-2278) update JBT 4 / JBDS 6 Central to include latest 3rd party features

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2278: -------------------------------- Summary: update JBT 4 / JBDS 6 Central to include latest 3rd party features Key: JBDS-2278 URL: https://issues.jboss.org/browse/JBDS-2278 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rdPartyCertification, 3rdPartyDependencies, central, updatesite, Upstream Affects Versions: 6.0.0.Alpha2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 6.0.0.Beta1 We need to review the list of 3rd party features included in both JBT and JBDS Central and determine if we need/want to update to newer versions. Here's the complete list (not including org.jboss stuff): DONE: * mylyn (juno) - JBIDE-11469 * Google Plugin for Eclipse + Web Toolkit: http://code.google.com/p/google-plugin-for-eclipse/ - JBIDE-12497, JBDS-2235 TO BE REVIEWED * m2e 1.2 - JBIDE-12516 * egit 2.0 (juno) - JBIDE-12338 * GWT VE/WB: JBIDE-11167 * Android Tooling: JBIDE-12498 TO BE UPDATED? * subclipse + mylyn: http://subclipse.tigris.org/ * eclipse-cs (checkstyle): http://eclipse-cs.sourceforge.net/ * findbugs: http://findbugs.sourceforge.net/ * pmd: http://pmd.sourceforge.net/ * testng: http://testng.org/ * Jrebel: (latest from 3rd party site) * SpringIDE: http://www.springsource.com/developer -- 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, 4 months

1
19
0 / 0

[JBoss JIRA] (JBIDE-12568) CLONE - Bump PMD version in JBT/JBDS/Central to 3.2.6 (net.sourceforge.pmd.eclipse 3.2.4 has invalid OSGi MANIFEST.MF)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12568: ---------------------------------- Summary: CLONE - Bump PMD version in JBT/JBDS/Central to 3.2.6 (net.sourceforge.pmd.eclipse 3.2.4 has invalid OSGi MANIFEST.MF) Key: JBIDE-12568 URL: https://issues.jboss.org/browse/JBIDE-12568 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, central Affects Versions: 4.0.0.Alpha1 Environment: JBT 4.0.0.Alpha1 Reporter: Jiri Peterka Assignee: Nick Boldt Fix For: 3.3.2, 4.0.0.Alpha2 net.sourceforge.pmd.eclipse is not valid OSGI bundle and cannot be loaded as target runtime in eclipse It contains only: Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.0 Created-By: 10.0-b19 (Sun Microsystems Inc.) -- 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, 4 months

2
9
0 / 0

[JBoss JIRA] (JBIDE-11628) Improve perfs of aggregation script

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11628: -------------------------------------- Summary: Improve perfs of aggregation script Key: JBIDE-11628 URL: https://issues.jboss.org/browse/JBIDE-11628 Project: Tools (JBoss Tools) Issue Type: Enhancement Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 3.3.0.CR1 the aggregation script (build.xml) performs a lot of magic, such as collecting zips and source zips. Some steps may be obsolete and no more necessary, we should clean it to save execution time. -- 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, 4 months

3
10
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 October 2012