I found the proof of the issue.
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:
> 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?
> ----- "Dmitry Geraskov" <dgeraskov(a)exadel.com> wrote:
>> 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 ? :)
>>> 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 ;)
>>>>>>> Dmitry Geraskov wrote:
>>>>>>>> I can't delete attached file in svn.
>>>>>>>> As I remember I had the rights before.
>> Best regards,
>> Dmitry Geraskov
>> Senior Developer
>> Exadel Inc
>> jbosstools-dev mailing list
This is the second or third time you have changed some of my plugins'
icon locations and every time you do, it changes my icon from something
pretty into a big red box ;) Why do you keep changing the icon location
to add $nl$ in it? This breaks the icon. What is the reason for this?
Should I be keeping all my icons in separate folders for each language
even when the icon has no text in it?
For example, you change
And this breaks the icon.
Thanks in advance.
I noticed that there is not any KB builder/nature in our project
examples. And it's understandable since when Snjezana created examples
before we added this builder.
This builder is used for Code Assist and JSF EL Validation. If there is
not KB Builder in a project we will warn user (we also offer QuickFix
for this) and will work without it but with some limitation.
So let's add this builder to .project for example projects:
(This may not be of interest to everyone, but just thought I'd share it.
Also seeking ideas)
So I spent the better part of this week working on refining some of the
as-tools deployment api's and trying not to break anything (or if you
know me at all, purposely breaking things). I made a new plugin to hold
what is effectively an ssh deploy-only server. There's pretty much no UI
right now and everything's hard-coded, but I've gotten my first ssh
deployment working. ;)
None of this is in svn yet, but the one use-case I've gotten covered and
working is a zipped wtp-type project. So any project, a web project, ear
project, bpel / esb project, if the server has a property set to force
zipping of deployments, can now be deployed over ssh to some box that
Again, it's not in svn yet, and the UI is horrendous (read: not made at
all really) but the underlying APIs are there and I'll work on refining
it tomorrow to squeeze it into svn in some non-disgusting fashion.
** I was wondering if anyone had any good suggestions or what types of
settings you'd need for this type of server other than just host,
username, password, and hosts file. What type of functionality would you
want the server to provide you with if you were going to be deploying
Thanks in advance.
I don't recall if I ever brought this up or if someone else did. Does
anyone have problems with the eclipse installation complaining about the
drools-core.jar in the workspace? Has it ever been addressed / fixed?
This is the error I get:
An internal error occurred during: "Building workspace".
jzentry == 0,
jzfile = 140319668613248,
total = 1226,
i = 303,
message = invalid LOC header (bad signature)
In regards to a jira (https://jira.jboss.org/jira/browse/JBIDE-5036) it
seems JDT does not like having jaxb-xjc.jar on the classpath of
projects. It's currently added by the runtime to the project in the
everything-and-the-kitchen-sink classpath management for servers.
The problem is jaxb-xjc.jar is malformed according to eclipse. It has a
folder inside it which is the parent to some packages and classes, but
this folder's name is "1.0" and eclipse is trying to treat it as a
package fragment but finds the name unacceptable.
Do we know of any projects that absolutely require jaxb-xjc.jar on the
classpath or should I add an exception and not include jaxb-xjc.jar from
the classpath containers?