[JBoss JIRA] (JBIDE-13639) remove struts tests from integration-tests update site
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13639?page=com.atlassian.jira.plugi... ]
Jiri Peterka closed JBIDE-13639.
--------------------------------
Verified, struts is removed from integration-tests
> remove struts tests from integration-tests update site
> ------------------------------------------------------
>
> Key: JBIDE-13639
> URL: https://issues.jboss.org/browse/JBIDE-13639
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, struts/shale
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-integration-tests.aggregate_master/53/console}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.struts.ui.bot.test 4.0.0.qualifier
> [ERROR] Missing requirement: org.jboss.tools.struts.ui.bot.test 4.0.0.qualifier requires 'bundle org.jboss.tools.struts.ui 3.1.0' but it could not be found
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.struts.ui.bot.test 4.0.0.qualifier to bundle org.jboss.tools.struts.ui 3.1.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
> {code}
> This is failing because struts has been removed from the upstream sites (it's been removed from JBT4.1/JBDS 7). So, need to also remove it from your integration tests site's category.xml file [1].
> [1] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si...
--
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-13463) Replace eclipse-update-site for aggregator by eclipse-repository
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13463?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-13463 at 3/7/13 4:10 AM:
----------------------------------------------------------------
Submitted PR https://github.com/jbosstools/jbosstools-build-sites/pull/34
[~nickboldt] Can you please review it?
I locally built the aggregate/site repository and its content seem to be OK (same bundles, same "facade" files).
This works because Ant scripts are ready to process category.xml as well as site.xml. Also it's not conflicting with the generate-repository-facade, although some tasks get performed twice.
Improvements of the Ant script and generate-repository-facade will be provided as part of JBIDE-11065 .
This is a necessary change for further pack200 and signing issues. Also, it's a first step to help us with fixing JBIDE-11065.
was (Author: mickael_istria):
Submitted PR https://github.com/jbosstools/jbosstools-build-sites/pull/34
[~nickboldt] Can you please review it?
This works because Ant scripts are ready to process category.xml as well as site.xml. Also it's not conflicting with the generate-repository-facade, although some tasks get performed twice.
Improvements of the Ant script and generate-repository-facade will be provided as part of JBIDE-11065 .
This is a necessary change for further pack200 and signing issues. Also, it's a first step to help us with fixing JBIDE-11065.
> Replace eclipse-update-site for aggregator by eclipse-repository
> ----------------------------------------------------------------
>
> Key: JBIDE-13463
> URL: https://issues.jboss.org/browse/JBIDE-13463
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha2
>
>
> The "eclipse-update-site" packaging type we've been using for aggregate sites is deprecated. Moreover it now shows some limitations (doesn't support pack.gz and other new Tycho stuff) that make it worth migrating to "eclipse-repository".
--
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-13731) error when creating html5 project from central: duplicate listener
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13731?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-13731:
---------------------------------------
You're right Stefan, this seems to be the same. But the other JIRA says it was fixed in Dali in Kepler. And this is Kepler. So somehow it broke again :( So let's keep this JIRA for Kepler.
> error when creating html5 project from central: duplicate listener
> ------------------------------------------------------------------
>
> Key: JBIDE-13731
> URL: https://issues.jboss.org/browse/JBIDE-13731
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Environment: JBDS 7.0.0.Alpha1c B124
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
>
> When you try to create the html5 project from JBoss Central, you get this error in the workspace log:
> {code}
> !ENTRY org.eclipse.jpt.jpa.core 4 0 2013-03-06 13:45:23.414
> !MESSAGE duplicate listener: AbstractJpaProject.ResourceModelListener[06-25-5B-29](HibernateJpaProject[7E-83-E3-E5](jboss-as-kitchensink-html5-mobile))
> !STACK 0
> java.lang.IllegalArgumentException: duplicate listener: AbstractJpaProject.ResourceModelListener[06-25-5B-29](HibernateJpaProject[7E-83-E3-E5](jboss-as-kitchensink-html5-mobile))
> at org.eclipse.jpt.common.utility.internal.ListenerList.add(ListenerList.java:95)
> at org.eclipse.jpt.common.core.resource.xml.JptXmlResource.addResourceModelListener(JptXmlResource.java:270)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe_(AbstractJpaProject.java:587)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe(AbstractJpaProject.java:560)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.synchronizeJpaFiles(AbstractJpaProject.java:1664)
> at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.synchronizeJpaFiles(HibernateJpaProject.java:264)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$InternalResourceDeltaVisitor.fileChangeIsSignificant(AbstractJpaProject.java:1649)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.fileChanged(AbstractJpaProject.java:1841)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visit(AbstractJpaProject.java:1833)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visitDelta(AbstractJpaProject.java:1816)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.internalProjectChanged(AbstractJpaProject.java:1627)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.projectChanged(AbstractJpaProject.java:1619)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.projectChanged_(InternalJpaProjectManager.java:759)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$ProjectChangeEventHandlerCommand.execute(InternalJpaProjectManager.java:741)
> at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {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, 1 month
[JBoss JIRA] (JBIDE-13747) [cleanup] expand org.jboss.ide.eclipse.as.ui.DeployMethodUI extension pt, allow for browse behavior
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13747?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-13747:
--------------------------------
Description: current browse behavior is embedded inside a specific internal class and the rse plugin reaches inside. This is a bad dynamic. Also allow for explore behavior as well. (was: current browse behavior is embedded inside a specific internal class and the rse plugin reaches inside. This is a bad dynamic. )
> [cleanup] expand org.jboss.ide.eclipse.as.ui.DeployMethodUI extension pt, allow for browse behavior
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13747
> URL: https://issues.jboss.org/browse/JBIDE-13747
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: JBossAS/Servers
> Affects Versions: 4.1.0.Alpha1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha2
>
>
> current browse behavior is embedded inside a specific internal class and the rse plugin reaches inside. This is a bad dynamic. Also allow for explore behavior as well.
--
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