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

[Design of JBoss Build System] - Re: jboss common maven build

by scott.stark＠jboss.org

"dimitris(a)jboss.org" wrote : That's my latest change (log4j.jar 1.2.8 -> 1.2.14) but how to upload the log4j. jar on the maven repository? | | I tried this and it will just store it on the local filesystem. | | X:\cvs\jboss-public\common\build>mvn install:install-file -DgroupId=apache-log4j | -DartifactId=log4j -Dversion=1.2.14 -Dpackaging=jar -Dfile=log4j.jar | | | To effectively use the repos as a local store and the path to push content into the repository, you need to setup your local repository to point to the cvs checkout of the repository.jboss.com/maven2 cvs module. This is done in your local ~/.m2/settings.xml or the mvn install conf/settings.xml. My settings.xml looks like: | [starksm@succubus Bios]$ cat ~/.m2/settings.xml | <settings> |  | <localRepository>/usr/Repository/repository.jboss.com/maven2</localRepository> | <profiles> | <profile> | <id>local-properties</id> | <properties> |  | <jboss.repository.root>/usr/Repository/repository.jboss.com</jboss.repository.root> |  | <maven.cvs.root>/usr/Repository/repository.jboss.com/maven2</maven.cvs.root> | </properties> | </profile> | </profiles> | | <activeProfiles> | <activeProfile>local-properties</activeProfile> | </activeProfiles> | </settings> | where the /usr/Repository/repository.jboss.com path is where I have checked out the repository.jboss.com contents. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032863#4032863 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032863

17 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: jboss common maven build

by scott.stark＠jboss.org

So let's get the first step of never looking to external repositories. Is this something that can be enforced at the project pom level, or does the user settings always allow for an override of the repo? A feature request we had from the start was to go a step further and allow a project to only load from signed repositories. I know Ruel brought this up in the maven dev lists and there was some interest, but I don't think any progress has been made. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032862#4032862 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032862

17 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Build System Meeting Agenda Mar 29, 2007

by pgier

Progress Since Last Meeting Updated JIRA, so the issues are up to date and schedule is now correct Microcontainer has been migrated fully to maven Released a new version of JBossRetro (bug fixes and minor interface changes. Release of jboss-retro-maven-plugin is scheduled for tomorrow (March 30th) Made some improvements to the jboss-deploy maven plugin and released version 1.1 IT created snapshot repository, they are still working on setting up access for all developers. IT started CVS to SVN migration Topics to Discuss Thirdparty repository - It would be helpful to have a thirdparty repository to separate all the non-jboss dependencies. Maybe a plugin can be created to copy a project's dependencies from the central repository to this thirdparty repo. Release process - next R&D meeting will include a discussion of the release process, what questions remain about this? Anything else? Goals for next meeting Work on CVS to SVN migration (repository.jboss.com, serialization, jbossretro) Release version 2 of the jboss-parent (includes retro and deploy plugins, some new eclipse configuration, and the snapshots repo) Create a wiki page with a list of jboss projects showing what stage of mavenization they are in. Finalize the new maven based release process View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032828#4032828 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032828

17 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: jboss common maven build

by pgier

I agree with you, our releases should be built entirely from our own repository. Right now we just don't have an easy way to copy things from the central repo when dependencies are updated. I will work on a new maven plugin (if I can't find an existing one) that can be used to copy a project dependency hierarchy from the central repository to our repository so that we have everything we need. I can set up version 3 of the jboss-parent pom so that it will only use the jboss repository when doing a release. This should be part of our release process. I would also like to have a new jboss repository just for third party dependencies. So we will have a releases repository, third party repository, and snapshot repository (for use during development). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032818#4032818 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032818

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: MDB/JCA adapter connection failures

by adrian＠jboss.org

This looks like an error in the MDB container or the resource adapter. The first error says the consumer can't deliver the message because the server session pool is not started: | I think the problem is fixed now. I changed the log4j dependency to point to the correct path. Log4j 1.2.14 was not in our repository, but it is in the central maven repository under /log4j/log4j. | What I don't see is an invocation of the ExceptionListener when it encounters this problem, instead it just logs a warning: | WARN 28-03 17:15:21,093 (JBossConnectionConsumer.java:run:303) -Connection consumer closing due to error in listening thread JBossConnectionConsumer[22, 1] | javax.jms.JMSException: Unable to get a server session java.lang.Exception: Cannot get a server session after the pool is stopped | which is useless for recovery. The rest of the log is NOISE that should not be there. Why log an error during close at ERROR level? It should be DEBUG at most, otherwise the user is not going to understand what the real problem is (in this case, it was already broken) - like Bill didn't, "Error closing a session" is not the problem it is a symptom. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032798#4032798 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032798

17 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: jboss common maven build

by adrian＠jboss.org

"pgier" wrote : I think the problem is fixed now. I changed the log4j dependency to point to the correct path. Log4j 1.2.14 was not in our repository, but it is in the central maven repository under /log4j/log4j. That's not a fix. We should be downloading everything from our repository. We need to guarantee that we have control over the bytes we ship. Which is just healthy paranoia. Not to mention that in my limited use of Maven so far, I've personally had at least three problems with stuff getting upgraded automatically inside maven that just doesn't work and breaks the build. This includes artifacts disappearing so it is impossible to even reproduce an earlier build. I'd prefer it if the maven repository (or any other) wasn't even checked when we download stuff for JBoss projects. We should be using a version of Maven from the jboss repository that we know works and more importantly in two years time, we can download the same version of Maven again to reproduce an old jboss project down to the exact byte. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032789#4032789 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032789

17 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: jboss common maven build

by pgier

"dimitris(a)jboss.org" wrote : That's my latest change (log4j.jar 1.2.8 -> 1.2.14) but how to upload the log4j. jar on the maven repository? | To upload to our repository you will have to commit the files to cvs under "repository.jboss.com". The files are already in the central maven repo though, so you don't have to worry about it for now. I'm working on an easier way to upload thirdparty artifacts like this, but for now it's just a cvs commit of the required jar and pom. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032788#4032788 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032788

17 years, 3 months

1
0
0 / 0

[Design of JBoss Portal] - Portlet messaging, please help

by Kborna

Hello all, Can some tell me how or provide me a sample code that shows the messaging between 2 different portles? Suppose I add 2 different portlets to a page, called PortletA and PortletB. PortletA has a form with a submit button. What I want to do is, when I submit the form from PortletA, I want the same information to appears on PortletB without me, refreshing the page? I know IBM WebSphere Portal has some APIs that allows messaging between portlets, but not sure if such thing exist on JSR 168? Can someone help me on this? Thanks Borna View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032785#4032785 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032785

17 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: jboss common maven build

by pgier

I think the problem is fixed now. I changed the log4j dependency to point to the correct path. Log4j 1.2.14 was not in our repository, but it is in the central maven repository under /log4j/log4j. I fixed the retro plugin and pointed the common build to version 0.5-SNAPSHOT version. For some reason jbossretro is not creating the classes-retro directory, and when the maven plugin couldn't find this folder it didn't fail gracefully. I will look into why the retro classes weren't created for logging-spi. Note: you may have to do a "mvn -U" to get the updated version. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032783#4032783 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032783

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - MDB/JCA adapter connection failures

by bill.burke＠jboss.com

http://jira.jboss.com/jira/browse/JBMESSAGING-930 I'm running a unit test in Embedded JBoss. Works fine most of the times. Randomly I'm getting the stack trace shown in 930 and no messages are ever delivered to the MDB. If I put a sleep after deployment of the MDB and Queue, everything works fine. The MDB also has an explicit dependency on the queue so it starts after the Queue starts. The only way I understand that this could happen is if the JMS inflow adapter tries to connect to Messaging in the background, or Queue initialization happens in a different thread. The is some race condition here obviously. Any insight? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032780#4032780 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032780

17 years, 3 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 March 2007