August 2006 - jboss-dev-forums - Jboss List Archives

[Design of JBossCache] - Re: Protected fields in TreeCache

by galder.zamarreno＠jboss.com

+1 on removing any protected fields. They should all be private with getter/setters where necessary. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962388#3962388 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962388

17 years, 9 months

1
0
0 / 0

[Design of JBoss Eclipse IDE (dev)] - Re: WAS: Hibernate Tools not forward compatible with WTP (@h

by max.andersen＠jboss.com

There are a couple of things here, first thing is that our feature.xml is apparently prohibiting people from using a later version of WTP ... we shouldn't (unless we know of a specific incompability, right ?) The other is how we package our stuff and Marshall lists the worstcase scenario of the number of packages. But looking at http://download.jboss.com/jbosside/builds/nightly/200608012131-nightly/bu... it isn't that bad is it ? Can't this be "cleaned" up ? e.g. instead of having core, jbossas and ejb3 tools as seperate plugins could they not be toghether ? When do you want them seperate ? Drools, AOP, Hibernate Tools, Designer and FreeMarker are the only "true" independent ones. And afaik Drools and FreeMarker are "true" independents in the word they don't need anything else but Eclipse leaving only AOP, Hibernate Tools and Designer as the only one that "needs" a "runtime-download" option. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962375#3962375 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962375

17 years, 9 months

1
0
0 / 0

[Design of JBoss Collaboration Server] - Re: Feature Request - I'll do the work!

by AronSogor

I think you do not want to runas the MBean. There should be context established when the user authenticates via SMTP/POP/IMAP. Use the users's realm. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962350#3962350 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962350

17 years, 9 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Why do I need to import the whole &tools module?

by ovidiu.feodorov＠jboss.com

When should we expect a migration? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962347#3962347 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962347

17 years, 9 months

1
0
0 / 0

[Design of JBoss Build System] - Re: build-thirdparty.xml <build> task attributes

by ovidiu.feodorov＠jboss.com

What exactly does the task do with them? Does it use them to create a descriptor or manifest of some sort? Is this explained somewhere on the wiki? Currently Messaging doesn't export any binary to the repository, but it should do it soon. I assume these attributes play a role in this process and I want to use them correctly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962345#3962345 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962345

17 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - CVS to SVN migration completed

by ovidiu.feodorov＠jboss.com

The CVS to SVN migration and separation of Messaging from the JBossAS source tree has been completed. The SVN repository is up and running and can be accessed at https://svn.jboss.org/repos/messaging/ For generic details on how to check out a JBoss project using SVN, please go to http://wiki.jboss.org/wiki/Wiki.jsp?page=SubversionMigrationGuide. I will soon update the Messaging wiki pages with specific examples. There are still open migration-related issues, but they are non-essential. For reference, they have been grouped as subtasks under http://jira.jboss.org/jira/browse/JBMESSAGING-455. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962343#3962343 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962343

17 years, 9 months

1
0
0 / 0

[Design of JBoss Build System] - Re: build-thirdparty.xml <build> task attributes

by scott.stark＠jboss.org

id = required identifier that matches the repository path. impl* = jar manifest impl* headers, unused description = info about what the binary does for humans cvsroot = the urn from which the binary source can be obtained View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962332#3962332 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962332

17 years, 9 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Why do I need to import the whole &tools module?

by scott.stark＠jboss.org

jbossbuild will be deprecated in favor of maven2. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962329#3962329 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962329

17 years, 9 months

1
0
0 / 0

[Design of JBoss Build System] - build-thirdparty.xml <build> task attributes

by ovidiu.feodorov＠jboss.com

I noticed that the taks has a series of attributes including "id", "impltitle", "implversion", "implvendor", "implurl", "description", "cvsroot", etc. How are these attributes intended to be used? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962326#3962326 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962326

17 years, 9 months

1
0
0 / 0

[Design of JBoss Build System] - Why do I need to import the whole &tools module?

by ovidiu.feodorov＠jboss.com

It seems that all I need in order to use jbossbuild with my project is tools/etc/jbossbuild/tasks.xml and toold/lib/jbossbuild.jar (and tools/etc/buildmagic/aliases.ent, it is required by jbossbuild but they it is useless to me, so it's just sitting there to make jbossbuild happy). I copied all these files over and imported in SVN and everything works fine. However, http://wiki.jboss.org/wiki/Wiki.jsp?page=ExampleBuildThirdparty advises to import the whole "tools" module, which contains a lot of useless buildmagic junk and then some. Is there any reason I should import the whole "tools" module instead of just copying jbossbuild.jar? How active do you predict jbossbuild will be in the future? Do you foresee the need of a lot of jbossbuild.jar updates? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962324#3962324 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962324

17 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2006