November 2010 - jbosstools-issues

[JBoss JIRA] Created: (TOOLSDOC-97) Hibernate_Tools_Reference_Guide | tasks-hibernate_mapping-persistent_classes

by Ben Clare (JIRA)

Hibernate_Tools_Reference_Guide | tasks-hibernate_mapping-persistent_classes ---------------------------------------------------------------------------- Key: TOOLSDOC-97 URL: https://jira.jboss.org/browse/TOOLSDOC-97 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Bug Components: Hibernate Affects Versions: 3.0.0.GA Reporter: Ben Clare Assignee: Ben Clare Testing assignement -- 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

15 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-85) Hibernate%20Tools%20Reference%20Guide%20|%203.2.

by Ben Clare (JIRA)

Hibernate%20Tools%20Reference%20Guide%20|%203.2. ------------------------------------------------ Key: TOOLSDOC-85 URL: https://jira.jboss.org/browse/TOOLSDOC-85 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Bug Components: Hibernate Affects Versions: 3.0.0.GA Reporter: Ben Clare Testing Feedback Link -- 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

15 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-116) JBDS40_045 Spring plug-ins (2.5.x and 3.0.x)

by Isaac Rooskov (JIRA)

JBDS40_045 Spring plug-ins (2.5.x and 3.0.x) -------------------------------------------- Key: TOOLSDOC-116 URL: https://jira.jboss.org/browse/TOOLSDOC-116 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Isaac Rooskov Assignee: Isaac Rooskov Tracker for this issue. Status: Uncommitted -> unsure if documentation is necessary -- 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

15 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-60) Releasing docs xslt and styles

by Svetlana mukhina (JIRA)

Releasing docs xslt and styles ------------------------------- Key: TOOLSDOC-60 URL: https://jira.jboss.org/jira/browse/TOOLSDOC-60 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.0.0.GA Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 3.0.1.GA Make a release version of docs xslt and styles https://snapshots.jboss.org/maven2/org/jboss/tools/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-104) JBDS40_012 Teiid Designer Reference Guide

by Isaac Rooskov (JIRA)

JBDS40_012 Teiid Designer Reference Guide ----------------------------------------- Key: TOOLSDOC-104 URL: https://jira.jboss.org/browse/TOOLSDOC-104 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Isaac Rooskov Assignee: Isaac Rooskov Priority: Blocker Tracker task for this issue. Status: Committed -- 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

15 years, 4 months

1
4
0 / 0

[JBoss JIRA] Resolved: (JBDS-1402) When publishing a file to ModeShape using JBDS, there should be the option to specifiy the "workspacepath", because this path is what the server looks for when determining what to sequence.

by Dan Florian (JIRA)

[ https://jira.jboss.org/browse/JBDS-1402?page=com.atlassian.jira.plugin.sy... ] Dan Florian resolved JBDS-1402. ------------------------------- Assignee: Dan Florian (was: Max Andersen) Resolution: Done Modified publishing wizard to allow the user to type in a workspace area. The workspace area is prepended to the file's project path and becomes the ModeShape workspace path for the file node created by the publishing operation. A bit better solution will be worked in JBDS-1403. > When publishing a file to ModeShape using JBDS, there should be the option to specifiy the "workspacepath", because this path is what the server looks for when determining what to sequence. > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-1402 > URL: https://jira.jboss.org/browse/JBDS-1402 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: Modeshape > Affects Versions: 4.0.0.Beta2 > Reporter: Van Halbert > Assignee: Dan Florian > Fix For: 4.0.0.Beta2 > > > When using the JBDS to publish to ModeShape, the option should be available to specify the "workspacepath". This path is what the server looks for when determining what to sequence. > The publish example in SOA specifies this argument and when the files are published, the sequenced information is appropriately seen in the expected tables (i.e., model:xmi). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBDS-1402) When publishing a file to ModeShape using JBDS, there should be the option to specifiy the "workspacepath", because this path is what the server looks for when determining what to sequence.

by Brian Fitzpatrick (JIRA)

[ https://jira.jboss.org/browse/JBDS-1402?page=com.atlassian.jira.plugin.sy... ] Brian Fitzpatrick commented on JBDS-1402: ----------------------------------------- Go for it. This sounds like a reasonable fix to squeeze in. > When publishing a file to ModeShape using JBDS, there should be the option to specifiy the "workspacepath", because this path is what the server looks for when determining what to sequence. > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-1402 > URL: https://jira.jboss.org/browse/JBDS-1402 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: Modeshape > Affects Versions: 4.0.0.Beta2 > Reporter: Van Halbert > Assignee: Max Andersen > Fix For: 4.0.0.Beta2 > > > When using the JBDS to publish to ModeShape, the option should be available to specify the "workspacepath". This path is what the server looks for when determining what to sequence. > The publish example in SOA specifies this argument and when the files are published, the sequenced information is appropriately seen in the expected tables (i.e., model:xmi). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-7624) Update RichFaces 4 libs to the just released M4 for JSF2 & RichFaces project templates.

by Alexey Kazakov (JIRA)

Update RichFaces 4 libs to the just released M4 for JSF2 & RichFaces project templates. --------------------------------------------------------------------------------------- Key: JBIDE-7624 URL: https://jira.jboss.org/browse/JBIDE-7624 Project: Tools (JBoss Tools) Issue Type: Task Components: JSF Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.0.Beta2 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBDS-1402) When publishing a file to ModeShape using JBDS, there should be the option to specifiy the "workspacepath", because this path is what the server looks for when determining what to sequence.

by Dan Florian (JIRA)

[ https://jira.jboss.org/browse/JBDS-1402?page=com.atlassian.jira.plugin.sy... ] Dan Florian commented on JBDS-1402: ----------------------------------- This change is needed because the current repository location that ModeShape Tools uses does not get sequenced. I checked-in a change to the publishing wizard to allow for a workspace path to be set. The workspace path defaults to "/files", which is the ModeShape default path, but the user can change it or clear it out if they want. Different workspaces may have different workspace paths. The wizard remembers the last path that was used. I verified that when the default workspace path is used, or any subfolder of the default path, the files are getting sequenced. However after check-in, I realized the change I just made caused other issues. Since users can change the workspace path whenever they use the publishing wizard, the same file can now be uploaded to multiple locations within the same repository. The PublishedLocationsDialog was implemented assuming a file could only appear in one location in the repository. So as it stands right now, this dialog only shows one location per workspace for each published file. And what makes things even worse is the location that it shows does *not* include the workspace path. Obviously, this dialog needs to show all locations; each having the correct URLs. The changes I already made, along with the needed changes to PublishedLocationsDialog, would resolve this issue. However, there is a better way things can be done. Last night, ModeShape implemented a change (see https://jira.jboss.org/browse/MODE-1020) that would allow ModeShape Tools to query ModeShape for the workspace areas currently being sequenced for a given workspace. ModeShape Tools' publishing wizard could offer these choices to the user. > When publishing a file to ModeShape using JBDS, there should be the option to specifiy the "workspacepath", because this path is what the server looks for when determining what to sequence. > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-1402 > URL: https://jira.jboss.org/browse/JBDS-1402 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: Modeshape > Affects Versions: 4.0.0.Beta2 > Reporter: Van Halbert > Assignee: Max Andersen > Fix For: 4.0.0.Beta2 > > > When using the JBDS to publish to ModeShape, the option should be available to specify the "workspacepath". This path is what the server looks for when determining what to sequence. > The publish example in SOA specifies this argument and when the files are published, the sequenced information is appropriately seen in the expected tables (i.e., model:xmi). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-113) JBDS40_025 Eclipse 3.6.1 (Helios with SP1)

by Isaac Rooskov (JIRA)

JBDS40_025 Eclipse 3.6.1 (Helios with SP1) ------------------------------------------ Key: TOOLSDOC-113 URL: https://jira.jboss.org/browse/TOOLSDOC-113 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Isaac Rooskov Assignee: Isaac Rooskov Tracker for this issue. Status: Uncommitted. Uncertain if documentation is needed for the tasks that this encompasses. -- 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

15 years, 5 months

1
3
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 November 2010