Re: [jbosstools-dev] jira rights
by Dmitry Geraskov
Hi, Rodney,
I found the proof of the issue.
See https://jira.jboss.org/jira/browse/JBIDE-3712.
I updated there a few times file patch.rar.
So, helpdesk have to give back our rights! ;)
Rodney Russ wrote:
> Hmmmm, when I look at the Jira:
>
> https://jira.jboss.org/jira/browse/JBIDE-4527
>
> and click on the Manage Attachments link, I don't see any way to delete an attachment either. I'm not sure what the "delete" interface looked like. Should this be forwarded to the helpdesk?
>
> -Rodney
>
> ----- "Dmitry Geraskov" <dgeraskov(a)exadel.com> wrote:
>
>
>> https://jira.jboss.org/jira/secure/ManageAttachments.jspa?id=12388792
>>
>> I want to delete older id_detail.png.
>>
>>
>> Max Rydahl Andersen wrote:
>>
>>> delete old attachment of what ? Got a jira issue so I can look ? :)
>>>
>>> /max
>>>
>>> Dmitry Geraskov wrote:
>>>
>>>> There is a problem. I can't delete old attachment.
>>>>
>>>> Max Rydahl Andersen wrote:
>>>>
>>>>> Okey - so there are no problems ?
>>>>>
>>>>> Dmitry Geraskov wrote:
>>>>>
>>>>>> Not in svn, but in jira. I was mistaken.
>>>>>>
>>>>>> Max Rydahl Andersen wrote:
>>>>>>
>>>>>>> delete what file ? Nothing were attached - and even if it were I
>>>>>>>
>>>>>>> would still need to know its location to answer ;)
>>>>>>>
>>>>>>> /max
>>>>>>>
>>>>>>> Dmitry Geraskov wrote:
>>>>>>>
>>>>>>>> I can't delete attached file in svn.
>>>>>>>> As I remember I had the rights before.
>>>>>>>>
>> --
>> Best regards,
>>
>> Dmitry Geraskov
>> dgeraskov(a)exadel.com
>> Senior Developer
>> Exadel Inc
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
--
Best regards,
Dmitry Geraskov
dgeraskov(a)exadel.com
Senior Developer
Exadel Inc
14 years, 7 months
Re: Moving to XulRunner 1.9
by Maksim Areshkau
On Tue, 2009-05-19 at 08:27 -0400, Max Rydahl Andersen wrote:
> > > I don't have the resources to promise that the javaxpcom will
> > work/be
> > > maintained so i guess for now we will just continue to bundle the
> > > eclipse/mozilla custom built one so any security issues is not
> > exposed
> > > in the general browser but only in the development tooling
> > > where it is less of an issue since it is primarily used to access
> > > local sites.
> > >
> > > /max
>
> > What does this mean for question move VPE on xulrunner 1.9 or not?
> > /Maksim Areshkau
>
> That beyo8nd xulrunner 1.9 removing features we depend on we now also
> need someone to maintain the xpcom interfaces...afaik ATF did that before.
Java XPCOM bridge provided by mozilla, what doing ATF gays - just
provided a plugin with this interfaces, if so it's not difficult to do.
> Who does it now ?
>
> /max
Almost all xpcom interfaces that used by us has frozen status and
shouldn't changed, so this doesn't needed to change something.
--
Maksim Areshkau
14 years, 10 months
Large projects for tests ? Why ?
by Max Rydahl Andersen
Hi,
Is it really necessary for us to have multiple copies of the same jars
in all the new tests projects in
C:\work\os\jbosstools\trunk\jst\tests\org.jboss.tools.jst.jsp.test\projects
?
how many of these jars are actually relevant for the test ?
/max
14 years, 11 months
Re: [jbosstools-dev] Status for JBDS and Tools documentation. docs created by Exadel doc team
by Dmitry Geraskov
Svetlana Mukhina wrote:
> here is a list of up-to-date docs created by Exadel doc team -
> http://download.jboss.org/jbosstools/nightly-docs/
>
>
> On Tue, 2009-08-25 at 09:54 +0300, Dmitry Geraskov wrote:
>
>> Could I use http://www.redhat.com/docs/ to see a list of all your
>> available docs? Or http://docs.jboss.org/tools/?
>> What are the docs written by Exadel's doc team of the list?
>>
>> Svetlana Mukhina wrote:
>>
>>> Anastasiya Bogachuk
>>> Last week:
>>> Context menu unification for the VPE and for the text editor - JBDS-787
>>> Properties and Outline views: description - JBDS-788
>>> Screenshots – content correspondence verification - JBDS-358
>>>
>>> This week:
>>> Context menu unification for the VPE and for the text editor - JBDS-787
>>> Properties and Outline views: description - JBDS-788
>>> Screenshots – content correspondence verification - JBDS-358
>>>
Is the same contents for two weeks a mistake or?
>>> Olga Chukhutina
>>> Last week:
>>> -updated all out-of-date screens of VPE in Seam-Doc,
>>> JSF-doc,Struts-Doc,Birt-Doc,GSG,Doc-VisualWebTools.Other guides were
>>> checked.JBDS-796
>>> -described CSS Preview in CSS Editing Perspective chapter in Doc -
>>> VisualWebTools. JBDS-812
>>> -described JBoss CSS Editing Perspective in Doc - VisualWebools:
>>> new chapter CSS Editing Perspective was created.JBDS-825
>>>
>>> This week:
>>> -will update Smooks guide according to the new changes.JBDS-821
>>> -will add "XSD Input Data Selection" Wizard description to Doc-Smooks.
>>> JBDS-796
>>>
>>>
>>> Olga Chikvina:
>>> Last week:
>>> - looking through the Forum posts. JBDS-671
>>> - updating the Visual Web Tools guide according to implemented
>>> preliminary support for JSF 2.0. JBDS-820
>>> - the guides update according to EAP 5 support in JBDS 2.1
>>> implemented. JBDS-836
>>>
>>> Next week:
>>> - will continue looking through the Forum posts. JBDS-671
>>> - the guides update according to EAP 5 support in JBDS 2.1
>>> implemented. JBDS-836
>>>
>>> Mukhina Svetlana
>>> last week
>>> JBDS-814 VPE support for facelets packed in jar file is implemented -
>>> all guides are looked through, sections for update are defined, waiting
>>> for JBIDE-4778 to resolve.
>>> JBDS-740 Links as Pronounce were replace with more meaningful phrases
>>> JBDS-685 Hibernate Configuration File opened in different ways; JBDS-823
>>> JBoss icons new style is updated,
>>> JBDS-727 Dev jira tasks review for Tools 3.1.0 release
>>>
>>> current week
>>> JBDS-799 Search in property file using regular expressions is
>>> implemented
>>> JBDS-810 JBDS release: preparing a doc bundle
>>> JBDS-837 OpenOn works for testNG XML files opened in JBoss XML Editor
>>> JBDS-840 CSS editor is redesigned
>>> JBDS-841 VPE templates for JSTL tags are added
>>>
>>>
>>>
--
Best regards,
Dmitry Geraskov
dgeraskov(a)exadel.com
Senior Developer
Exadel Inc
14 years, 11 months
How to save preferences in .settings folder
by Rob Stryker
Hi All:
I previously thought using an project-scoped preference eclipse
preference node would properly store the data in your project so that
the preference is a per-project setting and so that also these
preferences can be shared.
This is not the case, as from this article:
* /Project scope/. This scope stores values that are specific to a
single project in your workspace, such as code formatter and
compiler settings. Note that this scope is provided by the
org.eclipse.core.resources plug-in, which is not included in the
Eclipse Rich Client Platform. This scope will not exist in
applications that don’t explicitly include the resources plug-in.
Settings saved in the following method, while on a project-scope, are
still saved in the workspace, which means they're not persisted to cvs /
svn / etc.
IScopeContext context = new ProjectScope(project);
IEclipsePreferences node = context.getNode(qualifier);
if (node != null)
node.putDouble(IJBossESBFacetDataModelProperties.ESB_PROJECT_VERSION, 2.0);
Does anyone know how to actually put some settings inside the .settings
folder of a project the way JDT and WTP do? Thanks.
14 years, 11 months
Re: [jbosstools-dev] How to save preferences in .settings folder
by Max Rydahl Andersen
Hi Denis, I assume you forgot to use reply all ;)
/max
Denis Maliarevich wrote:
> Also VPE settings are stored to the project's .settings folder using
> exactly the same way you've described.
>
> Max Rydahl Andersen wrote:
>> that is also my understanding.
>>
>> Rob, could you show the *exact* code you have done which doesn't
>> store it ?
>>
>> /max
>>
>> Alexey Kazakov wrote:
>>> We use exactly the same method, which you mentioned, to store Seam
>>> project settings in .setting folder.
>>> See
>>> org.jboss.tools.seam.ui.preferences.SeamSettingsPreferencePage.storeSettings()
>>>
>>>
>>> Rob Stryker wrote:
>>>> Hi All:
>>>>
>>>> I previously thought using an project-scoped preference eclipse
>>>> preference node would properly store the data in your project so
>>>> that the preference is a per-project setting and so that also these
>>>> preferences can be shared.
>>>>
>>>> This is not the case, as from this article:
>>>>
>>>> * /Project scope/. This scope stores values that are specific to a
>>>> single project in your workspace, such as code formatter and
>>>> compiler settings. Note that this scope is provided by the
>>>> org.eclipse.core.resources plug-in, which is not included in the
>>>> Eclipse Rich Client Platform. This scope will not exist in
>>>> applications that don’t explicitly include the resources
>>>> plug-in.
>>>>
>>>> Settings saved in the following method, while on a project-scope,
>>>> are still saved in the workspace, which means they're not persisted
>>>> to cvs / svn / etc.
>>>>
>>>> IScopeContext context = new ProjectScope(project);
>>>> IEclipsePreferences node = context.getNode(qualifier);
>>>> if (node != null)
>>>> node.putDouble(IJBossESBFacetDataModelProperties.ESB_PROJECT_VERSION,
>>>> 2.0);
>>>>
>>>>
>>>> Does anyone know how to actually put some settings inside the
>>>> .settings folder of a project the way JDT and WTP do? Thanks.
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
14 years, 11 months
Re: [jbosstools-dev] Status for JBDS and Tools documentation
by Dmitry Geraskov
Could I use http://www.redhat.com/docs/ to see a list of all your
available docs? Or http://docs.jboss.org/tools/?
What are the docs written by Exadel's doc team of the list?
Svetlana Mukhina wrote:
> Anastasiya Bogachuk
> Last week:
> Context menu unification for the VPE and for the text editor - JBDS-787
> Properties and Outline views: description - JBDS-788
> Screenshots – content correspondence verification - JBDS-358
>
> This week:
> Context menu unification for the VPE and for the text editor - JBDS-787
> Properties and Outline views: description - JBDS-788
> Screenshots – content correspondence verification - JBDS-358
>
> Olga Chukhutina
> Last week:
> -updated all out-of-date screens of VPE in Seam-Doc,
> JSF-doc,Struts-Doc,Birt-Doc,GSG,Doc-VisualWebTools.Other guides were
> checked.JBDS-796
> -described CSS Preview in CSS Editing Perspective chapter in Doc -
> VisualWebTools. JBDS-812
> -described JBoss CSS Editing Perspective in Doc - VisualWebools:
> new chapter CSS Editing Perspective was created.JBDS-825
>
> This week:
> -will update Smooks guide according to the new changes.JBDS-821
> -will add "XSD Input Data Selection" Wizard description to Doc-Smooks.
> JBDS-796
>
>
> Olga Chikvina:
> Last week:
> - looking through the Forum posts. JBDS-671
> - updating the Visual Web Tools guide according to implemented
> preliminary support for JSF 2.0. JBDS-820
> - the guides update according to EAP 5 support in JBDS 2.1
> implemented. JBDS-836
>
> Next week:
> - will continue looking through the Forum posts. JBDS-671
> - the guides update according to EAP 5 support in JBDS 2.1
> implemented. JBDS-836
>
> Mukhina Svetlana
> last week
> JBDS-814 VPE support for facelets packed in jar file is implemented -
> all guides are looked through, sections for update are defined, waiting
> for JBIDE-4778 to resolve.
> JBDS-740 Links as Pronounce were replace with more meaningful phrases
> JBDS-685 Hibernate Configuration File opened in different ways; JBDS-823
> JBoss icons new style is updated,
> JBDS-727 Dev jira tasks review for Tools 3.1.0 release
>
> current week
> JBDS-799 Search in property file using regular expressions is
> implemented
> JBDS-810 JBDS release: preparing a doc bundle
> JBDS-837 OpenOn works for testNG XML files opened in JBoss XML Editor
> JBDS-840 CSS editor is redesigned
> JBDS-841 VPE templates for JSTL tags are added
>
>
--
Best regards,
Dmitry Geraskov
dgeraskov(a)exadel.com
Senior Developer
Exadel Inc
14 years, 11 months
Problems with jira
by Maxim Areshkau
Hi,
I have tried to create a jira issue with following description and there
was an error.
Description[
/I have founded a couple more problems in "Add JSF capabilities" dialog
#1 When we click browse button it's show files select menus relativity
to folder where eclipse has been installed. It's should show files
select menu relative to project for which dialog has been called or
eclipse workspace. You can try for example create new file using СNTRL+N
menu and see how works file select dialog in eclipse.
#2 To add jsf capabilities i should select existing web.xml. I have
created simple java project, then created folder web, in this folder
created web.xml and select my web.xml in this dialog. After dialog has
finish the work in project was added one more web.xml descriptor.Why?/
]
Also i have tried to add this description as comment, and it wasn't work
too.
See errors on screen shots.
14 years, 11 months
Re: [jbosstools-dev] Diffenerent interpretation of NamingStrategy methods.
by Max Rydahl Andersen
>> The best solution is to check where NS is called inside Hibernate
>> Annotation and figure that out from here.
>> Here is a summary to get you started:
>> - classToTableName called when the table name is not explicit
>> - propertyToColumnName called when the column is not explicit on a
>> property
>> - tableName overrides an explicit table name
>> - overrides an explicit column name
>> - collectionTableName called fi the collection table is not explicit
>> - joinKeyColumnName called on a join key (explicit or implicit it seems)
>> - foreignKeyColumnName same for a FK
>> - logicalColumnName returns the name tht should be used in
>> @Annotations when referencing a given column (eg in @UniqueConstraint)
>> - logicalCollectionTableName same here
>> - logicalCollectionColumnName same here
>>
thanks for that list.
>> That being said, shouldn't you guys use the Hibenate metamodel instead?
sure, can it run on incomplete and possibly non-compiled classes being
edited live ?
/max
14 years, 11 months
Re: [jbosstools-dev] Fwd: Diffenerent interpretation of NamingStrategy methods.
by Max Rydahl Andersen
>>>>> It's a clusterfuck, sorry about that. We are all wrong except
>>>>> Max-the-manager. Oh the irony ;)
>>> heey! :)
>>>>> logicalColumnName is the name by which a column should be referred
>>>>> in metadata descriptors (like unique constraints, indexes etc). I
>>>>> don't think a user needs to use the logical mapping in HBM files
>>>>> (the metadata structure don't require it contrary to annotations).
>>>>> Anyway, the logical name should never appear in a physical column
>>>>> name, so HbmBinder #fail.
>>>>> http://opensource.atlassian.com/projects/hibernate/browse/HHH-4077
>>>>>
>>>>> I've attached a patch and applied it to trunk. It probably needs a
>>>>> quick test on your side and can be retrofitted to older versions.
>>> Doesn't this change the behavior radically ? ...and how should our
>>> validator know which sequence of calls it should use ...i hate bugs ;0)
>>
>> No it does not because realistically, doing an implementation
>> of logicalColumnName like the one in this test has no usecase.
>> What does the validator do exactly? I'm not clear how it should use
>> the NS.
The validator verifies that the column/tables used in the mappings
actually exists.
Thus we take the class and property, column and table names, put them
through NamingStrategy to see what physical name they will transform to
when you use the mappings at runtime.
>>> Looking in fisheye this change were done almost 4 years ago...
>>> http://fisheye.jboss.org/changelog/Hibernate?cs=8918
>>> for
>>> http://opensource.atlassian.com/projects/hibernate/browse/ANN-176
>>> where it seems to be done very deliberately ?
>>>
>>> are you sure this is a proper change ?
>>
>> Of course, I always do things deliberately but then I dont' remember.
>> In this case, I did fix the user bug by adding the
>> mapping.addColumnBinding() calls. I think back in the days, I thought
>> the logicalColumn should also be passed toNS.columnName. I think it
>> is wrong today.
>> In practice, MC.logicalColumn is almost always idempotent if the
>> column name is not null. That's why we have never seen any impact.
ok - but this means that our validator would need to use the
namingstrategy differently pre-3.5 and post-3.5. Just need's to know that ;)
/max
14 years, 11 months