January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10642) publisher/server adapter level include/excludes postprocessing

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10642: ------------------------------------------- Summary: publisher/server adapter level include/excludes postprocessing Key: JBIDE-10642 URL: https://issues.jboss.org/browse/JBIDE-10642 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.3.0.Beta1 -- 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

14 years, 2 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-10000) Decouple Forge Runtime and Forge Console

by Koen Aers (Created) (JIRA)

Decouple Forge Runtime and Forge Console ----------------------------------------- Key: JBIDE-10000 URL: https://issues.jboss.org/browse/JBIDE-10000 Project: Tools (JBoss Tools) Issue Type: Task Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.Beta1 These need to be decoupled so the Cmd+4 can run without the need for the textual console. Main usecase: scaffolding wizard. -- 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

14 years, 2 months

6
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7942) Add an image viewer (reusable via the QuickImage plugin)

by Juergen Zimmermann (JIRA)

Add an image viewer (reusable via the QuickImage plugin) -------------------------------------------------------- Key: JBIDE-7942 URL: https://issues.jboss.org/browse/JBIDE-7942 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Juergen Zimmermann QuickImage is an image viewer which is available as an Eclipse plugin. The homepage is http://psnet.nu/eclipse/index.html . It can be obtained via the Eclipse marketplace and seems to have the EPL license. Such a viewer is nice when you quickly want to inspect some images, icons, buttons etc. inside a web project. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
8
0 / 0

[JBoss JIRA] (JBIDE-10665) JBoss Tools don't know about Seam 2.3

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10665?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-10665: ---------------------------------------- Fred, take a look at http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/examples/... > JBoss Tools don't know about Seam 2.3 > ------------------------------------- > > Key: JBIDE-10665 > URL: https://issues.jboss.org/browse/JBIDE-10665 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Seam 2 > Affects Versions: 3.3.0.M5 > Environment: 2.3.0-SNAPSHOT, JBoss Tools Version: 3.3.0.v20111207-1453-H52-M5 > Reporter: Marek Novotny > Assignee: Alexey Kazakov > Fix For: 3.3.0.Beta1 > > > Imported project into latest JBoss Tools throws error while updating MAven dependencies in Seam Web project. -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10665) JBoss Tools don't know about Seam 2.3

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10665?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-10665: ------------------------------------- Marek, can you provide a test project I can use to test maven support? > JBoss Tools don't know about Seam 2.3 > ------------------------------------- > > Key: JBIDE-10665 > URL: https://issues.jboss.org/browse/JBIDE-10665 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Seam 2 > Affects Versions: 3.3.0.M5 > Environment: 2.3.0-SNAPSHOT, JBoss Tools Version: 3.3.0.v20111207-1453-H52-M5 > Reporter: Marek Novotny > Assignee: Alexey Kazakov > Fix For: 3.3.0.Beta1 > > > Imported project into latest JBoss Tools throws error while updating MAven dependencies in Seam Web project. -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10665) JBoss Tools don't know about Seam 2.3

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10665?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-10665: ----------------------------------- Issue Type: Feature Request (was: Bug) > JBoss Tools don't know about Seam 2.3 > ------------------------------------- > > Key: JBIDE-10665 > URL: https://issues.jboss.org/browse/JBIDE-10665 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Seam 2 > Affects Versions: 3.3.0.M5 > Environment: 2.3.0-SNAPSHOT, JBoss Tools Version: 3.3.0.v20111207-1453-H52-M5 > Reporter: Marek Novotny > Assignee: Alexey Kazakov > Fix For: 3.3.0.Beta1 > > > Imported project into latest JBoss Tools throws error while updating MAven dependencies in Seam Web project. -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-7565) Problems publishing and accessing parent pom + target platforms

by Nick Boldt (JIRA)

Problems publishing and accessing parent pom + target platforms --------------------------------------------------------------- Key: JBIDE-7565 URL: https://jira.jboss.org/browse/JBIDE-7565 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.2.0.Beta2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.2.0.CR1 Thought I had this solved, but on further testing, I've found a problem. This file is 404'd: http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o... However, the one I actually published is fine: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... So, when I try to retrieve the pom from the repo, I get this error: [DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://repository.jboss.org/nexus/content/groups/public/ Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o... [DEBUG] Reading resolution tracking file /home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/resolver-status.properties [DEBUG] Writing resolution tracking file /home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/resolver-status.properties [DEBUG] Could not find metadata org.jboss.tools:org.jboss.tools.target.platform:0.0.1-SNAPSHOT/maven-metadata.xml in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) [DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://repository.jboss.org/nexus/content/groups/public/ Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o... [DEBUG] Reading resolution tracking file /home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/org.jboss.tools.target.platform-0.0.1-SNAPSHOT-unified.target.lastUpdated [DEBUG] Writing resolution tracking file /home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/org.jboss.tools.target.platform-0.0.1-SNAPSHOT-unified.target.lastUpdated [ERROR] Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools:org.jboss.tools.target.platform:target:unified:0.0.1-SNAPSHOT -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools:org.jboss.tools.target.platform:target:unified:0.0.1-SNAPSHOT How can I force the resolution process to look at https://repository.jboss.org/nexus/content/repositories/snapshots instead of http://repository.jboss.org/nexus/content/groups ? Or, how can I force the missing/empty file to contain the correct versioning information so that maven can find the artifact? I also tried to switch from <uniqueVersion>true</uniqueVersion> to <uniqueVersion>false</uniqueVersion> but the published artifacts still have the uniqueVersion suffixes. ---------- Steps to reproduce: # remove your existing local .m2 cache if [[ -d ~/.m2 ]]; then mv ~/.m2 ~/.m2___GOOD; fi # check out build folder cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/build/ # check out tests folder cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/tests/ # build tests cd /tmp/tests; mvn3 clean install -X -e -fae -U -B Workaround: However, if the parent pom is built locally, then the tests can be built too, w/o a problem (because the parent pom + target platform artifacts now exist locally in my ~/.m2 folder): # build parent pom + target platform cd /tmp/build; mvn3 clean install -f parent/pom.xml # build tests cd /tmp/tests; mvn3 clean install -X -e -fae -U -B ---------- Here's how I'm building + publishing the artifacts, fwiw: http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta2.target-platf... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
13
0 / 0

[JBoss JIRA] (JBIDE-10441) Hibernate Configuration launcher file opens Hibernate Console Dialog by default

by Jiri Peterka (Created) (JIRA)

Hibernate Configuration launcher file opens Hibernate Console Dialog by default ------------------------------------------------------------------------------- Key: JBIDE-10441 URL: https://issues.jboss.org/browse/JBIDE-10441 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: hibernate Affects Versions: 3.3.0.M4 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta1 Steps: Create Hibernate Console Configuration and store it in as a launcher file in a project. Try to open it. It's opened in a plain text editor. I would like to see opening via Hibernate Configuration dialog (as similar as when I click on Hibernate Configuration item in Hibernate Console Configuration view). It have to be recognized according to it's content because filename/extension is general for all launchers (*.launcher). -- 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

14 years, 2 months

9
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8058) smooks test fails when run w/ all other tests (incl. emma code coverage), but passes when run solo (no emma)

by Nick Boldt (JIRA)

smooks test fails when run w/ all other tests (incl. emma code coverage), but passes when run solo (no emma) ------------------------------------------------------------------------------------------------------------ Key: JBIDE-8058 URL: https://issues.jboss.org/browse/JBIDE-8058 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.2.0.CR1 Reporter: Nick Boldt Assignee: Brian Fitzpatrick Priority: Optional Passes: http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2... Passing for at least the last 4 builds (Since #8) > mvn3 clean install -B -U -fae -e -Dmaven.repo.local=${WORKSPACE}/m2-repository -P helios-local-target,jbosstools-nightly-trunk,hudson --- Fails: http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2... Failing for the past 43 builds (Since #216 ) > mvn3 clean install -B -U -fae -e -Dmaven.repo.local=${WORKSPACE}/m2-repo -P helios-local-target,jbosstools-nightly-trunk,hudson,coverage --- I'm not sure this is a big deal, I'm just curious why this is happening. Ideally, the same test should pass in both scenarios. Could it be related to emma code coverage? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8043) Two different context menus for OnMessage/OnAlarm

by Marek Baluch (JIRA)

Two different context menus for OnMessage/OnAlarm ------------------------------------------------- Key: JBIDE-8043 URL: https://issues.jboss.org/browse/JBIDE-8043 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.Beta2, 3.2.0.CR1 Environment: JBoss Tools: 3.2_trunk.2010-12-16_04-27-01-H504 Reporter: Marek Baluch Priority: Minor It's possible to get 2 context menus for OnMessage and OnAlarm branch. While both are usable only one of them is consistent with other context menus for similar activities. The first (IMO correct one) allows to add activities to the branch in question while the other does not. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
12
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 2012