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

[Design of JBoss Build System] - Re: jboss-parent 4-beta-2

by pgier

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: jboss-parent 4-beta-2

by pgier

jdk 1.3 is the default that the maven compiler plugin uses if you don't specify anything. I had removed this from the new version of the parent so that projects would have to specify what java version they want to use, but we can add it back if it's better that way. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142905#4142905 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142905

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: jboss-parent 4-beta-2

by alesj

Now I'm getting compilation error, due to 1.3 jdk usage: | [ERROR] BUILD FAILURE | [INFO] ------------------------------------------------------------------------ | [INFO] Compilation failure | | C:\projects\microcontainer\mdr\src\main\org\jboss\metadata\spi\retrieval\helper\MetaDataToAnnotationBridge.java:[36,39] generics are not supported in -source 1.3 | (try -source 1.5 to enable generics) | public class MetaDataToAnnotationBridge<T extends Annotation> implements AnnotationItem<T> | Where is this 1.3 jdk creeping in? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142904#4142904 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142904

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: jboss-parent 4-beta-2

by adrian＠jboss.org

Previous occurance of this "bug" http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131164 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142896#4142896 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142896

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: jboss-parent 4-beta-2

by alesj

This is what I get when running dry release:prepare | [INFO] Scanning for projects... | [INFO] NOTE: Using release-pom: C:\projects\microcontainer\mdr\release-pom.xml in reactor build. | [INFO] ------------------------------------------------------------------------ | [INFO] Building JBoss MetaData Repository | [INFO] task-segment: [clean, verify] | [INFO] ------------------------------------------------------------------------ | [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from repository.jboss.org | [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from snapshots.jboss.org | [INFO] ------------------------------------------------------------------------ | [ERROR] BUILD ERROR | [INFO] ------------------------------------------------------------------------ | [INFO] Failed to resolve artifact. | | GroupId: org.apache.maven.plugins | ArtifactId: maven-assembly-plugin | Version: RELEASE | | Reason: Unable to determine the release version | | org.apache.maven.plugins:maven-assembly-plugin:pom:RELEASE | There is this line in release-pom.xml: | <artifactId>maven-assembly-plugin</artifactId> | <version>RELEASE</version> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142892#4142892 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142892

18 years

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBPAPP-750 - Integration between AS and JBossMessaging 1

by adrian＠jboss.org

"timfox" wrote : "adrian(a)jboss.org" wrote : | | But for JBoss 5, how about making an explicit distinction between the QueueFactoryRef and the XAQueueFactoryRef etc. | | | | Or even something as simple as a "UseXA" on the JMSProvider config. | But its still going to fail when it is configured inconsistently. | | If I thought there really was a use case, then we could create | a simpler <jms-connection-factory/> xml tag like we do | for datasources in the -ds.xml which would avoid the misconfiguration. | | Maybe the misconfiguration problem is actually the use case that I'm looking | for to justify spending time on this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142890#4142890 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142890

18 years

1
0
0 / 0

[Design of JBoss Build System] - jboss-parent 4-beta-2

by adrian＠jboss.org

I did a new release of jboss parent which will generate release poms during the tagging part of the release process. I also noticed 4-beta-1 didn't have the correct compiler settings like version 3 had. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142884#4142884 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142884

18 years

1
0
0 / 0

[Design of Security on JBoss] - Re: Security Injection in AS5

by adrian＠jboss.org

No, you don't need a seperate parsing deployer in this case (you could have one if you wanted say a META-INF/security-policy.xml in any deployment that automatically creates a security policy for the deployment). What you do need is the metadata model (in this case your BeanMetaDataFactory) available before it starts deploying the runtime, i.e. before anything in deploy is processed. If you don't do that, then somebody adding a jbsx:policy to their config, (e.g. jboss messaging or jca could do this) may or may not be parsable based on whether the classes have been deployed and the jbossxb config done. In practice the classes will never be deployed since the initial bootstrap does a breadth first parse of all config in the deploy before proceeding to create classloaders (in the future when we move over to more locked down classloading dependencies we'll need to know whether a deployment wants the ejb classes first, i.e. does it have an ejb component). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142882#4142882 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142882

18 years

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBPAPP-750 - Integration between AS and JBossMessaging 1

by timfox

"adrian(a)jboss.org" wrote : | Like I said above. There's no way for the resource adapter to know that the administrator | configured a local connection manager. So there's no way for us avoid the | subtle failures when things get misconfigured. | With the current configuration, yes. I accept no-one wants to introduce config changes for AS 4.x right now. But for JBoss 5, how about making an explicit distinction between the QueueFactoryRef and the XAQueueFactoryRef etc. (Looking at the glassfish jms ra config I can see they allow them to be specified separately.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142879#4142879 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142879

18 years

1
0
0 / 0

[Design of Security on JBoss] - Re: Security Injection in AS5

by anil.saldhana＠jboss.com

Separating the deployment model from the runtime in the case of DynamicLoginConfig means that the xml config that is getting injected into the beans needs to be moved out in to the deployers (parsing deployer ?). This means for an user to inject one instance of a security domain configuration (eg: messaging or JBossWS) into the security system will need to add the bean configuration in -beans.xml in the deploy directory and add a parsing deployer for his xml driving the sec.domain in the deployers directory. Is my understanding correct? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142873#4142873 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142873

18 years

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 April 2008