What is our release schedule for JBTools 3.1?
If it's at all convenient, we might want to synchronize with (or shortly
after) the WTP 3.1 release and the Galileo maintenance release. This way
we can be developing on their stream and notice their bugs.
Their release for GA is June 24. That's 4 months away. If we plan on
releasing at, around, or after that, we might wan t to switch our dev
stream to the integration builds they pump out.
There is a problem about classpath.
Up to now, the jboss ws module of our tools use two commands --
'wsprovider.bat' and 'wsconsumer.bat' -- to generate codes
in both scenes: bottow-up(from a java class) and top-down(from a wsdl file).
When we call wsprovider.bat to generate codes, we may create a command
to run in our eclipse console like this:
wsprovider -c 'a.jar:b.jar:c.jar.............xxx.jar' -w -k
My codes run this command like this in my plugins:
Runtime rt = Runtime.getRuntime();
rt.exec(command.toString(), null, new File(commandLocation));
On linux, this is ok. But on windows, a error occurs: the command is too
long. This is caused by the classpath parameter is
too long because we add very many jars to '-c'
I think, in enterprise scenes, we will often meet this problem -- need
to add many jars to classpath.
So I want to ask if we have a way to set a container or a jars folder
for these jars.
Sounds great - can we do it from the early mornings ?
When do you arrive ?
Mark Newton wrote:
> Hi Max,
> Looks good :)
> As we've now fully released the Magnolia CMS we'd like to help you
> move your pages over as soon as possible. I'll be in Neuchatel
> tomorrow if you want to meet in person so we can go through the
> process together. This will probably be the quickest way to get things
> On 8 Mar 2009, at 21:47, Max Rydahl Andersen wrote:
>> I want our main website to be simpler than it is now - I did a very
>> quick prototype for this at http://jboss.org/tools/ga
>> Please let me know what you think.
>> p.s. ignore the left link bar - it will either be removed or reduced
>> in final version, but I can't remove it without affecting the current
>> p.p.s. I plan on adding a "news" section and possibly a page per main
>> functionality linked to from the front page - but not sure I can make
>> that happen before GA (lot's of typing :).
>> p.p.p.s. The doc page is not finished (actually no page is finished
>> since it is a quick prototype)
>> p.p.p.p.s. I hope Mark Newton will tell me we can move to the new
>> Magnolia CMS driving the new sites at jboss.org, but I haven't
>> heard anything final yet so to be ready with this for 11th I needed
>> to do something in the current mechanism.
> Mark Newton
> JBoss Community Lead
> Mobile: +41 7657 47730
> Office: +41 41 728 7253
> Skype: callto://newtonmark
> Email: mark.newton(a)jboss.org
I found a \r\n sequence in the key Error_WS_Chose_runtime of
When I convert this to a Gettext pot file, it warns about the \r being
non-portable. It probably isn't all that non-portable, but I would like
to eliminate the warning. It looks like this string is eventually
passed to this Eclipse API method:
Is there any reason we can't remove the \r, and leave the \n?
Any idea if the \r is significant?
Senior Software Engineer
Engineering - Internationalisation
The reason build #22 throws the same exception is that the metadata
generator is called before adding JBT plugins (the studio and links
dirs). There isn't any JBT plugin in bundles.info.
It is necessary to add the studio and links dir before calling the
metadata generator app.
The p2.os option probably isn't obliged because bundles.info is updated
Now we have MyFaces 1.1.4 among jsf KickStart projects. But VPE
doesn't support tomahawk templates. And it looks like funny when you
open page from supported test project and see that it is not all supported ;)
Maybe need to exlude MyFaces Kickstart from the list of kickstart
Anton Klimkovich mailto:firstname.lastname@example.org