May 2009 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: Uploading MC artifacts to the labs downloads area

by pgier

The problem is that any profile with activation "activeByDefault" will be deactivated if another profile is activated. This is a bad "feature" of Maven IMO because it's counter-intuitive to most people. As a work around you can explicitly activate the default profile and do something like. | mvn -Passembly,default install -Dmaven.test.skip | In general I would recommend not using activeByDefault and instead using a not well documented feature of the property activation to make a profile activeByDefault. So it looks something like this. | <profile> | <id>default</id> | <activation> | <property>!skip.default.profile</property> | </activation> | <properties> | </profile> | This tells maven that the profile "default" is active unless the property "skip.default.profile" is set. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232789#4232789 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232789

15 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Websphere MQ with XA connections

by tfennelly

After getting a copy of the Extended Client Config, I was at last able to reproduce this issue and verify that the mods made to the JmsConnectionPool (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155230) solved it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232784#4232784 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232784

15 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Default VFS caching locations

by jason.greene＠jboss.com

"alesj" wrote : | Or if the newly/additionally added "deploy" folder is not high volume, | does it still make sense to permanently cache it? | The problem is that the current deployers & VFS design is *very* dependent on permanent caching of VFS roots, per the discussion here: http://lists.jboss.org/pipermail/jboss-development/2009-April/014187.html So, anything which doesn't use it will eventually fail (unless they aren't using temps). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232783#4232783 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232783

15 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Jar dependencies chapter

by clebert.suconic＠jboss.com

+1 on 4. Too many JARs. and it would be easier to redistribute it as one jar. Don' t know if there are license issues with trove and jaxb used by the MicroContainer though. Can we repack and redistribute a jar? (I know there are some restrictions.. sometimes you can as long as you mention license terms.. .I" m not sure) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232780#4232780 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232780

15 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Uploading MC artifacts to the labs downloads area

by kabir.khan＠jboss.com

Paul, Now that I have fixed the docs I have a new problem: | [kabir(a)~/sourcecontrol/microcontainer/tags/2.0.6.GA/subversion] | $mvn -Passembly install -Dmaven.test.skip | [INFO] Scanning for projects... | [INFO] Reactor build order: | [INFO] JBoss Microcontainer Parent POM | [INFO] JBoss Microcontainer Dependency | [INFO] JBoss Microcontainer Kernel | [INFO] JBoss Microcontainer AOP MC INT | [INFO] JBoss Microcontainer Spring Int | [INFO] JBoss Microcontainer Guice Int | [INFO] JBoss Microcontainer Distribution Build | [INFO] JBoss Microcontainer Docs | [INFO] JBossMC Getting Started Guide (en_US) | [INFO] JBossMC Getting Started Guide (aggregator) | [INFO] JBossMC Reference Guide (en_US) | [INFO] JBossMC Reference Guide (aggregator) | WAGON_VERSION: 1.0-beta-2 | .... | [INFO] Building JBoss Microcontainer Kernel | [INFO] task-segment: [install] | [INFO] ------------------------------------------------------------------------ | [INFO] [enforcer:enforce {execution: enforce-versions}] | [INFO] [resources:resources] | [INFO] Using default encoding to copy filtered resources. | [INFO] [compiler:compile] | [INFO] Compiling 409 source files to /Users/kabir/sourcecontrol/microcontainer/tags/2.0.6.GA/subversion/kernel/null | [INFO] ------------------------------------------------------------------------ | [ERROR] BUILD FAILURE | [INFO] ------------------------------------------------------------------------ | [INFO] Compilation failure | | /Users/kabir/sourcecontrol/microcontainer/tags/2.0.6.GA/subversion/kernel/src/main/java/org/jboss/beans/metadata/spi/builder/BeanMetaDataBuilder.java:[42,32] package org.jboss.dependency.spi does not exist | | /Users/kabir/sourcecontrol/microcontainer/tags/2.0.6.GA/subversion/kernel/src/main/java/org/jboss/beans/metadata/spi/builder/BeanMetaDataBuilder.java:[43,32] package org.jboss.dependency.spi does not exist | ... | I have looked in the kernel/pom.xml, but can't see anything obvious that would be affected by the -Passembly switch? Also, I notice that a normal 'mvn install' has this output for the kernel module | [INFO] Compiling 409 source files to /Users/kabir/sourcecontrol/microcontainer/tags/2.0.6.GA/subversion/kernel/target/classes | I don't know if that is significant or not? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232779#4232779 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232779

15 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Jar dependencies chapter

by clebert.suconic＠jboss.com

For 1) I' ve listed the dependencies on the JARs versus feature. I will try to make it more explicity though. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232778#4232778 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232778

15 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Trying to install libaio

by clebert.suconic＠jboss.com

You also need to have ./trunk/native/bin on LD_LIBRARY_PATH. We should also document this. export LD_LIBRARY_PATH=./path-to-trunk/native/bin View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232777#4232777 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232777

15 years, 1 month

1
0
0 / 0

[Design of JBossCache] - Re: Evolution of TcpDelegatingCacheLoaders/TcpCacheServers

by akluge

Hi, I have had chance to get back to this, and have made some good progress. I have a cache client and server, both built with MINA, and that use a binary protocol for put and get requests. Some interesting points - The performance is good (<1ms/ async request) - A request submission returns a Future, and multiple requests can be sent, and their results recovered later. The TCPDelegating cache loader, however, immediatly waits on the future. I have run into one issue. For a cache miss, the CacheLoaderInterceptor always loads the entire cache under the FQN, even if allKeys is false. To me, this is not an optimal solution for a large scale solution. I would want to load only the specific missed value when a get fails. Is there a reason to always load the enire cache under the FQN on a cache miss? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232775#4232775 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232775

15 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Uploading MC artifacts to the labs downloads area

by kabir.khan＠jboss.com

This problem also extends to several poms in docs/ subfolders, I am committing these changes as well. | [kabir(a)~/sourcecontrol/microcontainer/tags/2.0.6.GA/subversion] | $svn diff | Index: docs/gettingstarted/en-US/pom.xml | =================================================================== | --- docs/gettingstarted/en-US/pom.xml (revision 89292) | +++ docs/gettingstarted/en-US/pom.xml (working copy) | @@ -2,7 +2,7 @@ | <parent> | <groupId>org.jboss.microcontainer.docs</groupId> | <artifactId>jboss-microcontainer-docs</artifactId> | - <version>2.0.0-SNAPSHOT</version> | + <version>2.0.6.GA</version> | </parent> | <modelVersion>4.0.0</modelVersion> | <groupId>org.jboss.microcontainer</groupId> | @@ -43,4 +43,4 @@ | <translation>en_US</translation> | </properties> | | -</project> | \ No newline at end of file | +</project> | Index: docs/gettingstarted/pom.xml | =================================================================== | --- docs/gettingstarted/pom.xml (revision 89292) | +++ docs/gettingstarted/pom.xml (working copy) | @@ -3,7 +3,7 @@ | <parent> | <groupId>org.jboss.microcontainer.docs</groupId> | <artifactId>jboss-microcontainer-docs</artifactId> | - <version>2.0.0-SNAPSHOT</version> | + <version>2.0.6.GA</version> | </parent> | <modelVersion>4.0.0</modelVersion> | <groupId>org.jboss.microcontainer.docs</groupId> | Index: docs/reference/en-US/pom.xml | =================================================================== | --- docs/reference/en-US/pom.xml (revision 89292) | +++ docs/reference/en-US/pom.xml (working copy) | @@ -2,7 +2,7 @@ | <parent> | <groupId>org.jboss.microcontainer.docs</groupId> | <artifactId>jboss-microcontainer-docs</artifactId> | - <version>2.0.0-SNAPSHOT</version> | + <version>2.0.6.GA</version> | </parent> | <modelVersion>4.0.0</modelVersion> | <groupId>org.jboss.microcontainer</groupId> | @@ -43,4 +43,4 @@ | <translation>en_US</translation> | </properties> | | -</project> | \ No newline at end of file | +</project> | Index: docs/reference/pom.xml | =================================================================== | --- docs/reference/pom.xml (revision 89292) | +++ docs/reference/pom.xml (working copy) | @@ -3,7 +3,7 @@ | <parent> | <groupId>org.jboss.microcontainer.docs</groupId> | <artifactId>jboss-microcontainer-docs</artifactId> | - <version>2.0.0-SNAPSHOT</version> | + <version>2.0.6.GA</version> | </parent> | <modelVersion>4.0.0</modelVersion> | <groupId>org.jboss.microcontainer</groupId> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232773#4232773 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232773

15 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Uploading MC artifacts to the labs downloads area

by kabir.khan＠jboss.com

Problem: microcontainer/tags/2.0.6.GA/docs/pom.xml contained the wrong version (2.0.3-SNAPSHOT) which in turn makes it impossible to do a release build | [kabir@~/sourcecontrol/mcrelease/microcontainer] | $mvn -Passembly -Dmaven.test.skip=true install | [INFO] Scanning for projects... | Downloading: http://snapshots.jboss.org/maven2/org/jboss/microcontainer/jboss-microcon... | [INFO] ------------------------------------------------------------------------ | [ERROR] FATAL ERROR | [INFO] ------------------------------------------------------------------------ | [INFO] Failed to resolve artifact. | | GroupId: org.jboss.microcontainer | ArtifactId: jboss-microcontainer | Version: 2.0.3-SNAPSHOT | | Reason: Unable to download the artifact from any repository | | org.jboss.microcontainer:jboss-microcontainer:pom:2.0.3-SNAPSHOT | | from the specified remote repositories: | central (http://repo1.maven.org/maven2), | repository.jboss.org (http://repository.jboss.org/maven2), | snapshots.jboss.org (http://snapshots.jboss.org/maven2) | | | [INFO] ------------------------------------------------------------------------ | [INFO] Trace | org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.jboss.microcontainer:jboss-microcontainer for project: org.jboss.microcontainer.docs:jboss-microcontainer-docs:pom:null for project org.jboss.microcontainer.docs:jboss-microcontainer-docs:pom:null | at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) | at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) | at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) | at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) | at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) | at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) | at org.codehaus.classworlds.Launcher.main(Launcher.java:375) | Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.jboss.microcontainer:jboss-microcontainer for project: org.jboss.microcontainer.docs:jboss-microcontainer-docs:pom:null for project org.jboss.microcontainer.docs:jboss-microcontainer-docs:pom:null | at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370) | at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821) | at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506) | at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198) | at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) | at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) | at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534) | at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) | ... 11 more | Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.jboss.microcontainer:jboss-microcontainer' not found in repository: Unable to download the artifact from any repository | | org.jboss.microcontainer:jboss-microcontainer:pom:2.0.3-SNAPSHOT | | from the specified remote repositories: | central (http://repo1.maven.org/maven2), | repository.jboss.org (http://repository.jboss.org/maven2), | snapshots.jboss.org (http://snapshots.jboss.org/maven2) | for project org.jboss.microcontainer:jboss-microcontainer | at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:603) | at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1366) | ... 18 more | Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository | | org.jboss.microcontainer:jboss-microcontainer:pom:2.0.3-SNAPSHOT | | from the specified remote repositories: | central (http://repo1.maven.org/maven2), | repository.jboss.org (http://repository.jboss.org/maven2), | snapshots.jboss.org (http://snapshots.jboss.org/maven2) | | at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212) | at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) | at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:556) | ... 19 more | Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository | at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:331) | at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:200) | ... 21 more | [INFO] ------------------------------------------------------------------------ | [INFO] Total time: 1 second | [INFO] Finished at: Fri May 22 16:36:58 BST 2009 | [INFO] Final Memory: 2M/4M | [INFO] ------------------------------------------------------------------------ | I have updated the docs pom in the tag to use the correct version. I know we will have this problem in deployers and possibly man as well (cl is fine). Paul says it is because the maven build does not include the docs in the normal build since they take considerable time to build, but from what I gather this also means they do not get included when the release plugin updates the version numbers, so this currently needs doing by hand. For the current releases I will update the docs versions in the tag's poms. But I don't think this is something we should keep doing, both for the obvious 'don't touch the tag' reason, but also to avoid having to manually fiddle with something that we are trying to automate :-) Also, the script uses anonsvn, so there is the normal time-lag issue of changes done in proper svn getting replicated to anonsvn. I know we have started the process of moving docs to a separate svn location, am I correct in assuming that once this is done the problem I am seeing will disappear? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232771#4232771 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232771

15 years, 1 month

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 May 2009