January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13254) In Seam 2.3 seam-gen generated project imported in JBDS, EL completion for Seam Messages doesn't work

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13254?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBIDE-13254: --------------------------------------- Alexey, what is correct project setting for that? Could you point me at some template/example of dynamic web project with JSF and Seam facets? > In Seam 2.3 seam-gen generated project imported in JBDS, EL completion for Seam Messages doesn't work > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13254 > URL: https://issues.jboss.org/browse/JBIDE-13254 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2, UpStream > Affects Versions: 3.3.1, 4.0.0.Beta2 > Environment: WFK 2.1.0.CR2 Seam.2.3.0.Final-redhat-1, JBDS 5.0.1.GA, JBDS 6.0.0.Beta2a > Reporter: Ron Šmeral > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha1 > > > After importing a Seam 2.3 seam-gen generated project in JBDS, the EL completion for Seam Messages doesn't work. > This works OK for a Seam project created in JBDS and for a Maven project imported to JBDS. > > Actual results: > Even though the "messages" component is suggested, no actual messages from the properties files are suggested. A warning is shown for e.g #{messages['org.jboss.seam.NotLoggedIn']}. > Expected results: > Messages from messages_xx.properties should be suggested without warnings. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13301) Need a new core test - ESB runtime detection - to successfully test for ESB version 4.11

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13301?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-13301: ----------------------------------- Assignee: Brian Fitzpatrick (was: Rob Stryker) I've added a unit test to esb via this PR: https://github.com/jbosstools/jbosstools-esb/pull/7 It's awaiting approval. I am not 100% sure if this is what test you're asking for. Basically, this is verifying that esb 4.11 is an acceptable module type for specific jboss app servers. It also tests all other versions for esb. I do not expect this test should be accepted as-is. Or rather, I expect it is accepted, but that the ESB team tells me what is clearly wrong. Specifically, if AS 4.2 should support some other list of versions. At that point, a new jira should be opened. > Need a new core test - ESB runtime detection - to successfully test for ESB version 4.11 > ---------------------------------------------------------------------------------------- > > Key: JBIDE-13301 > URL: https://issues.jboss.org/browse/JBIDE-13301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.0.0.Final > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.1.0.Alpha1 > > > Related to: > https://issues.jboss.org/browse/JBDS-2394#comment-12741206 > <nboldt> ldimaggi: do any of the as.core tests involve esb 4.11? > <nboldt> ldimaggi: open a jira for rawblem to add a test for JBT 4.1 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13347) Add deltaspike jars into nexus repository (releases/snapshots)

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13347?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-13347: ------------------------------------------- I have solved my problem by adding jboss nexus public repo into pom.xml of deltaspike bot tests. > Add deltaspike jars into nexus repository (releases/snapshots) > -------------------------------------------------------------- > > Key: JBIDE-13347 > URL: https://issues.jboss.org/browse/JBIDE-13347 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: UpStream > Reporter: Jaroslav Jankovič > Assignee: Mickael Istria > > Now, deltaspike libraries are not in jboss nexus repositories defined in our shared settins.xml (releases/snapshots). They are part of central jboss nexus repo but this one is not used when building swtbot tests. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13336) create target platform using Kepler dependencies

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13336?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13336: ---------------------------------------- [~fbricon]: The purpose of this TP is to get something as close as possible to what will be in Kepler. So we'll use the 1.3 milestones for m2e. > create target platform using Kepler dependencies > ------------------------------------------------ > > Key: JBIDE-13336 > URL: https://issues.jboss.org/browse/JBIDE-13336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > Attachments: multiple.target, multiple.target_update_hints.txt > > > Along with the refactoring we talked about doing in JBIDE-13232, it's time to create a new Kepler M4 target platform. > I've pulled mirrors for the three largest pieces: Kepler M4, Eclipse 4.3M4, WTP 3.5M4: > http://download.jboss.org/jbosstools/updates/requirements/kepler/20121221... > http://download.jboss.org/jbosstools/updates/requirements/eclipse/S-4.3M4... > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5.... > Do you need anything else mirrored? If so bounce this to me and I'll get the bits copied to download.jboss.org for you. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-13213: ------------------------------------------- Rob, as you can see in my first comment - you have to have archives view closed when replicating it. > Simple adding/removing Project Archives capabilities into project > ----------------------------------------------------------------- > > Key: JBIDE-13213 > URL: https://issues.jboss.org/browse/JBIDE-13213 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Reporter: Vlado Pakan > Assignee: Rob Stryker > Fix For: 3.3.2 > > > It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-13213: ------------------------------------------- Oh, I forgot. I am using JBDS 5.0.2 CR2 > Simple adding/removing Project Archives capabilities into project > ----------------------------------------------------------------- > > Key: JBIDE-13213 > URL: https://issues.jboss.org/browse/JBIDE-13213 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Reporter: Vlado Pakan > Assignee: Rob Stryker > Fix For: 3.3.2 > > > It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-13213: ------------------------------------------- Rob, there are no extra steps to perform. Are you sure, you are replicating it on a fresh workspace? I am able to replicate it always Only workaround I found is opening the archives view and select a project in it. This magically triggers archives node behaviour also in project explorer. (now I am able to right-click) > Simple adding/removing Project Archives capabilities into project > ----------------------------------------------------------------- > > Key: JBIDE-13213 > URL: https://issues.jboss.org/browse/JBIDE-13213 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Reporter: Vlado Pakan > Assignee: Rob Stryker > Fix For: 3.3.2 > > > It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders

by Jesper Skov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ] Jesper Skov commented on JBIDE-13346: ------------------------------------- Bad wording on my part: I don't see any bad behavior (that I'm aware of), the log output is, as you say, a warning. > DirectoryScanner fails on non-existing folders > ---------------------------------------------- > > Key: JBIDE-13346 > URL: https://issues.jboss.org/browse/JBIDE-13346 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives, JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: Windows XP/Windows 7 > Eclipse 4.3M4 > Reporter: Jesper Skov > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > Attachments: org.eclipse.wst.common.component > > > DirectoryScanner can be made to fail on non-existing folders. > In our setup, these folders are possibly picked up from the Deployment Assembly settings. > The folders are created by our custom Builder with highest priority, so appears to work properly with everything else in Eclipse. > But it seems the Archive DirectoryScanner runs before our builder. > The stack trace looks like this: > > {code} > java.lang.IllegalStateException: basedir C:\udvikler\ws\plugins\jb.it.reuters\build\gen-lib-deployable is not a directory > at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scanPrepare(DirectoryScanner.java:552) > at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scan(DirectoryScanner.java:588) > at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:66) > at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent$WorkspaceFilter.<init>(WorkspaceFilesetVirtualComponent.java:100) > at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent.getRootFolder(WorkspaceFilesetVirtualComponent.java:53) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.consumeComponent(FlatVirtualComponent.java:203) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:196) > at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.optimize(ClasspathLibraryExpander.java:47) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:119) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:101) > at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.fetchResource(ClasspathLibraryExpander.java:74) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:463) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:208) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:540) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:311) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:295) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:336) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:321) > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13213: ------------------------------------- Jaroslav: I'm not able to replicate that. It seems to be adding the node, adn I can right-click the node immediately. Are there any more steps to replicate here? Which version are you testing on? > Simple adding/removing Project Archives capabilities into project > ----------------------------------------------------------------- > > Key: JBIDE-13213 > URL: https://issues.jboss.org/browse/JBIDE-13213 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Reporter: Vlado Pakan > Assignee: Rob Stryker > Fix For: 3.3.2 > > > It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13213: ------------------------------------- Also please see if there's any workaround, such as closing the view and re-opening it? > Simple adding/removing Project Archives capabilities into project > ----------------------------------------------------------------- > > Key: JBIDE-13213 > URL: https://issues.jboss.org/browse/JBIDE-13213 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Reporter: Vlado Pakan > Assignee: Rob Stryker > Fix For: 3.3.2 > > > It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly. -- 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, 6 months

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 January 2013