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

[Design the new POJO MicroContainer] - JBVFS 2.0.0.Beta10/2.0.0.CR1 releases

by scott.stark＠jboss.org

We need a vfs release with bug fixes for current jbossas issues, but there are too many open issues for the current 2.0.0.Beta10, so we need another release 2.0.0.Beta10 can be done prior to jbossas5.0.0.CR1. These release needs to be a CR1 release as well. I have created 2.0.0.CR1 2.0.0.GA, and 2.0.1.Beta1 release targets. Most of the current 2.0.0.Beta10 issues will be moved to 2.0.0.CR1. These need to be further paired down to what will realistically get done for 2.0.0.GA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134045#4134045 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134045

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: VFS serialization

by scott.stark＠jboss.org

With the current vfs trunk which includes a fix for JBVFS-17, the JBCTS-752 webservice test is passing for me. I'll create a snapshot for this so the cts runs can resume. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134043#4134043 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134043

18 years, 1 month

1
0
0 / 0

[Javassist development Forum] - Re: Javassist version 3.6.0.GA maven2

by skarzhevskyy

Is there the person responsible for uploading latest Javassist to maven central repository? How this is done in jboss.com? If this is regular manual process I can suggest myself to do this. I'm uploading 3rd party projects like: proguard.sourceforge.net regularly. Also I maintain bluecove.org microemu.org and jour.sourceforge.net. They all need the latest Javassist in repository. My project are uploaded to central repository automatically by rsync. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134028#4134028 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134028

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: jndiName

by bytor99999

"adrian(a)jboss.org" wrote : "bytor99999" wrote : 21:47:32,843 WARN [ManagementViewImpl] Failed to create ManagedDeployment for: MarkDS-ds.xml | | org.jboss.deployers.spi.DeploymentException: Context MarkDS-ds.xml not found | | at org.jboss.deployers.plugins.main.MainDeployerImpl.getDeploymentContext(MainDeployerImpl.java:173) | | at org.jboss.deployers.plugins.main.MainDeployerImpl.getManagedDeployment(MainDeployerImpl.java:650) | | at org.jboss.profileservice.management.ManagementViewImpl.loadProfile(ManagementViewImpl.java:186) | | | | At least part of the problem is that you are passing the wrong deployment name here. OK, I looked at the code, and in this case I am not passing that value at all Here is the last bit of code in that stack from our code at org.rhq.plugins.jbossas5.factory.ProfileServiceFactory.refreshCurrentProfileView(ProfileServiceFactory.java:1 02) This is that method | public static void refreshCurrentProfileView() | { | try | { | Profile activeProfile = getProfileService().getActiveProfile(); | ProfileKey activeKey = activeProfile.getKey(); | getCurrentProfileView().loadProfile(activeKey); | } | catch (Exception e) | { | LOG.error("Could not find default Profile in Current Profile View", e); | } | } | We are just refreshing our managementView Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134011#4134011 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134011

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: aop-mc-int tests failing on annotation parsing

by alesj

"alesj" wrote : | I'll assign an issue to Kabir for the previous (delegate vs. proxy) failures. | - http://jira.jboss.com/jira/browse/JBMICROCONT-250 "alesj" wrote : | And this last one to me, commenting on the 'fix' that I did. | - http://jira.jboss.com/jira/browse/JBMICROCONT-251 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134008#4134008 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134008

18 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Re: Maven downloads

by scott.stark＠jboss.org

Absolutely. Isn't this a requirement for Fedora using a maven repo for any bundled contents? I don't see how else they have an auditable path to the source for every component. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134005#4134005 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134005

18 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Re: Maven downloads

by pgier

Yes, this is an ongoing problem. It's just difficult to keep up with the dependency changes. I think we need to have our own rsync'ed mirror of the central repository. That way we can have a copy of everything controlled by us. And we won't have this issue of continuously checking new dependencies into our repository. WDYT? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134000#4134000 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134000

18 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Re: Problem running tests in microcontainer/aop-mc-int

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | I'll try blowing away my entire local repository. That usually fixes these issues, | Old faithful. If its not working, hit it with a hammer. ;-) Its working now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133996#4133996 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133996

18 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Maven downloads

by adrian＠jboss.org

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: cts config startup issue with current vfs trunk

by scott.stark＠jboss.org

This particular error seems to be due to old code coming in. On another box with clean builds, the error is due to serialization of JBVFS-17. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133990#4133990 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133990

18 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2008