RemoteSystemsTempFiles
by Galder Zamarreno
Hi,
Can someone explain why at my JBDS trunk workspace a folder called
"RemoteSystemsTempFiles" is being generated?
Inside, there's a .project file with the following contents:
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>RemoteSystemsTempFiles</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
</buildSpec>
<natures>
<nature>org.eclipse.rse.ui.remoteSystemsTempNature</nature>
</natures>
</projectDescription>
Thanks,
--
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
16 years, 8 months
QA Daily report 14 January 2009
by Aliaksey Nis
Hello Denis,
This is Daily QA report for 14 January 2009.
Tasks performed:
1. Testing of JBoss Tools and JBDS CR2 latest builds.
Test reports will be uploaded tomorrow.
2. Issues verification.
--
Best regards,
Aliaksey mailto:anis@exadel.com
16 years, 8 months
Invalid zip file format for WS and JBPM plugins
by Galder Zamarreno
Hi,
I'm trying to install latest from tools nightly update site and I'm getting:
An error occurred while collecting items to be installed
Problems downloading artifact:
osgi.bundle,org.jboss.tools.ws.creation.ui,1.0.0.CR2-N200901131921.
Exception connecting to
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb....
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb...
Exception connecting to
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb....
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb...
Error closing the output stream for
org.jboss.tools.ws.feature/org.eclipse.update.feature/1.0.0.CR2-N200901131921
on repository file:/opt/tools/.
Error unzipping
/tmp/org.jboss.tools.ws.feature_1.0.0.CR2-N2009011319215914191937094379930.jar:
Invalid zip file format
Problems downloading artifact:
osgi.bundle,org.jboss.tools.ws.ui,1.0.0.CR2-N200901131921.
Exception connecting to
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb....
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb...
Exception connecting to
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb....
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb...
Problems downloading artifact:
osgi.bundle,org.jbpm.gd.jpdl,3.1.5.CR2-N200901131921.
Exception connecting to
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb....
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb...
Exception connecting to
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb....
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb...
Error closing the output stream for
org.jbpm.gd.jpdl.feature/org.eclipse.update.feature/3.1.5.CR2-N200901131921
on repository file:/opt/tools/.
Error unzipping
/tmp/org.jbpm.gd.jpdl.feature_3.1.5.CR2-N2009011319216312381732928111616.jar:
Invalid zip file format
and also:
An error occurred while collecting items to be installed
Problems downloading artifact:
osgi.bundle,org.jbpm.gd.jpdl,3.1.5.CR2-N200901131921.
Exception connecting to
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb....
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb...
Exception connecting to
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb....
http://download.jboss.org/jbosstools/updates/nightly/trunk/plugins/org.jb...
Error closing the output stream for
org.jbpm.gd.jpdl.feature/org.eclipse.update.feature/3.1.5.CR2-N200901131921
on repository file:/opt/tools/.
Error unzipping
/tmp/org.jbpm.gd.jpdl.feature_3.1.5.CR2-N200901131921764529311882957663.jar:
Invalid zip file format
Cheers,
--
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
16 years, 8 months
Re: importing soa samples to jbds
by Max Rydahl Andersen
>
> I uploaded some SOA examples into a JBDS format:
>
> https://www.yousendit.com/download/WnBTQmtld0E0b0RIRGc9PQ
>
> It's more clear and simplyfied structure,
you mean the "JBDS format" is more clear and simplified than the
original SOA examples or ?
> I think that may be can help to JBDS team to create some templates to
> create "New ESB project" or similar.
Denny/Grid - is this something you can look into ?
/max
>
> I hope this helps.
>
> Lucas
>
> Max Rydahl Andersen escribió:
>> You mean the soa samples that comes with SOA ?
>>
>> They are not structured in any way for the IDE to figure out where
>> and what the resources are so not easily doable - require manual
>> tweaking.
>>
>> Try out Help > Project Examples - here Grid and Denny have migrated
>> some basic examples to a more IDE friendly format.
>>
>> p.s. I've added the jbosstools list so I'm not the only one hearing
>> about this.
>>
>> /max
>>> Higuys,
>>> does any have tips for importing the soa sample to jbds/eclipse?
>>> when I try to import it I only get the src file imported but nothing
>>> else, like the process def.
>>>
>>> thanks
>>> Alejandro
>>
>
16 years, 8 months
Question on Good Practice Re: Servers and Runtimes
by Rob Stryker
Currently, server and runtime objects in wtp have "names", the
displayable value, and "ids", the value in their serialized file which
links together the various pieces.
In the past, I used the WTP default of a timestamp-type "id", and
assigned names to the server and runtime objects. But it was discovered
that doing that made it almost impossible to "share" this server object
in a repository. The server would reference some vague timestamped
runtime, and it would be impossible to create a runtime of that
timestamp really.
So I switched to having the name and the id be exactly the same. The
side effect of this is that, when you change the runtime or server's
name, you're changing it's "id" also, and so by changing a runtime's
name, any server's that link to it now point to a not-found runtime.
This is in addition to any projects that referenced that runtime.
This is very related to JBIDE-3391, where the user changed the runtime's
name from within the server editor, but then did *not* save the dirty
server editor to update the reference. This broke his deployment, and
though the JIRA doesn't mention it, the user would actually not be able
to re-open the server editor =P Admittedly this issue is the user's
fault as he didn't save the dirty server editor... but if he had changed
the runtime's name from the runtime preference window, instead of the
editor, there'd be no recourse *at all*. ALL the servers and projects
would reference a stale nonexistent runtime object.
Since the default Runtime id is a timestamp-like string, it assumes that
you can change the name all you want, and that doing so will not create
stale objects. But months ago we decided we liked having names as our id
instead of random timestamp strings. I'm honestly not sure what to do
here. It's obvious to me that the id must be an unchanging string and a
timestamp is as good as any...
Look forward to input.
16 years, 8 months
Re: importing soa samples to jbds
by Max Rydahl Andersen
You mean the soa samples that comes with SOA ?
They are not structured in any way for the IDE to figure out where and
what the resources are so not easily doable - require manual tweaking.
Try out Help > Project Examples - here Grid and Denny have migrated some
basic examples to a more IDE friendly format.
p.s. I've added the jbosstools list so I'm not the only one hearing
about this.
/max
> Higuys,
> does any have tips for importing the soa sample to jbds/eclipse? when
> I try to import it I only get the src file imported but nothing else,
> like the process def.
>
> thanks
> Alejandro
16 years, 8 months
