July 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Build System] - Re: Sources are not picked up from snapshots

by bstansberry＠jboss.com

Great. :) I'd opened a JIRA https://jira.jboss.org/jira/browse/JBAS-5813 and have now closed it. As I use stuff I'll add source attributes to the .classpath files. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167434#4167434 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167434

17 years, 5 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Remoting and remote classloading

by scott.stark＠jboss.org

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167421 is the thread for the related JBREM-1019 issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167431#4167431 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167431

17 years, 5 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Sources are not picked up from snapshots

by scott.stark＠jboss.org

I changed copySourceJars=true by default so sources are now downloaded by default. To build without source just pass in -DcopySourceJars=false. No new profile is needed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167430#4167430 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167430

17 years, 5 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Sources are not picked up from snapshots

by skajotde

Sorry, my answer were cut by forum parser. It is without quote: I think the same. Earlier I have worked on simple project with 20 maven 1.x modules. Editing with eclipse was horrible. maven 1.x even doesn't resolve dependent projects and only leave dependencies to maven repository No I'm working on big project with 150 maven 2 modules ! Fortunately maven 2 eclipse plugin better resolve project despondencies but sucks with classpath ordering and editing 150 .classpath is unacceptable without some templating system (not necessary maven ;)). I know that 150 modules cause system much more modular ;) and it is need in some cases but it cant block developing and reffactoring. Correct configured IDE is essential and need well-thought-out build system. Without this, modularizies is over marketed IMHO and very slows developing. My brother works on 3 modules project in Netbeans, not maven, Yes, one centrized IDE but deploying cycle occupy only 5 seconds with all sources available ! Short deploing cycle is critical to developing IMHO. I'm sometimes frustrated with modularization without proper configruation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167426#4167426 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167426

17 years, 5 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Sources are not picked up from snapshots

by skajotde

"bstansberry(a)jboss.com" wrote : | But... I still say downloading sources should be the default behavior., and we should be adding source="/thirdparty/..." attributes in .classpath files as we go. If poking around in the AS source code had been anywhere near as hard in 2003 as it is now, I never would have started as a community member. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167425#4167425 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167425

17 years, 5 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Sources are not picked up from snapshots

by skajotde

"bstansberry(a)jboss.com" wrote : | But... I still say downloading sources should be the default behavior., and we should be adding source="/thirdparty/..." attributes in .classpath files as we go. If poking around in the AS source code had been anywhere near as hard in 2003 as it is now, I never would have started as a community member. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167424#4167424 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167424

17 years, 5 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Sources are not picked up from snapshots

by scott.stark＠jboss.org

I don't disagree. It looks like the profile would then have to be no-download-sources to and a change of the copySourceJars property to true by default. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167422#4167422 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167422

17 years, 5 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - JBREM-1019, RemotingClassLoader parent first behavior

by scott.stark＠jboss.org

For the jbossas5 app client container, a class loader policy that loads from the child first is used to pickup the client jar manifest references. If such a class loader is registered as the user class loader with the RemotingClassLoader, its not going be delegated to first. This results in duplicate and conflicting classes being loaded. There needs to be an option to delegate to the user class loader before the parent. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167421#4167421 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167421

17 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Remoting refactoring complete

by clebert.suconic＠jboss.com

I could only run it fine with 90K or less. with 100K + starts to fail. I don't know why... this is just what I have seen happening. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167419#4167419 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167419

17 years, 5 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Remoting and remote classloading

by scott.stark＠jboss.org

I'm running into a similar issue where the remoting class loader (org.jboss.remoting.loading.RemotingClassLoader) logic to ask the parent class loader before the user class loader is reversing the class loading policy of the javaee app client container. This results in inconsistent classes as bean interfaces are being loaded twice. At a minimum, there needs to be a parent first flag that allows the user class loader to be tried first. The description of the fix for JBREM-962 I see is too specific to the jboss4x class loader architecture, so I'm going to create a new issue for 2.4.0.GA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167417#4167417 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167417

17 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums July 2008