Log in to follow, share, and participate in this community.
Thread svn --non-interactive failing
svn --non-interactive failingI'm trying to release the common-logging-spi project using mvn release:prepare, and it keeps failing on the svn. It appears to be a specific issue with running svn with --non-interactive as if I run the same command o...
Build Contract for jbossall-client.jarI'm currently maintaining a separate assembly for the repackaging of jbossall-client.jar in the EJB3 Installer component, used when the EJB3 Plugin is run. Much like centralizing the dependencies between AS and AS co...
jboss metadata pomI'm making some changes to the jboss-metadata pom, for getting closer to a Beta7 release: - Updated to org.jboss.microcontainer:jboss-container:jar:2.0.0.Beta9 (was Beta6) - and removed the jboss:jbossxb exclusion (...
Thread Maven Version ranges - Snapshots during development
Maven Version ranges - Snapshots during developmentSo far I've done minimal testing of the version ranges themselves, but one issue I have found is that once you have a snapshot it will generally screw things up. I guess this is related to the bugs I linked on the oth...
Thread mvn deploy should have a precondition check for available ar
mvn deploy should have a precondition check for available arIt appears that a mvn deploy of a snapshot does not have a precondition check to see if all dependencies are really available. http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140796#4140796
Thread Dependency conflicts lost during AS mavenization
Dependency conflicts lost during AS mavenizationI am currently looking at two projects sharing a dependency, with each specifying a different version. During the AS build this conflict is not recognized anymore. I.e. the metadata project refers to jbossws-spi 1.0....
mvn dependency:treeAn 'mvn dependency:tree' from AS trunk/thirdparty with a semi-cleaned local maven repo takes almost half an hour for me. Is there a way to see the dependency tree without actually downloading all the .jar files locall...
Thread Maven Version ranges - Something rotten at repository.jboss.
Maven Version ranges - Something rotten at repository.jboss.While doing my version range testing, I can't get it to work over repository.jboss.org When I try to perform my release I get a bizzarre error message for this constraint
<dependency>
<groupId>junit&l...
Maven Version Ranges - Case sensitivityOne thing I found is that the qualifier being case sensitive is really confusing ;-) 1.0.0-beta-3 > 1.0.0-Beta-4 :-) 1.0.0-beta-3 > 1.0.0-GA Maybe we should stick to all lower case qualifiers to avoid typos ca...
Thread maven-metadata.xml and 'mvn release:perform'
maven-metadata.xml and 'mvn release:perform'While doing a jboss-common-core release, the following maven-metadata.xml was updated:https://svn.jboss.org/repos/repository.jboss.org/maven2/org/jboss/jboss-common-core/maven-metadata.xml a) I can see version 2.2.3....
Maven Version Ranges - SummarySee other threads for details and to make comments: DEPENDENCIES http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132677 The version ranges do actually work as they are supposed to, so if there weren...
Maven Version Ranges - DependenciesThe good news is the version ranges do actually work. The problem I described related to JBossAS doesn't exist if you use ranges. i.e. common-core has 1.0.1 and 1.0.2 jboss-aop 1.0.1 uses common-core 1.0.1 microconta...
Maven Version ranges - generateReleasePomsIn order to capture what was actually used to build the release you need to generate a release pom. This is a release-pom.xml that gets checked in when you tag the release in release:perform.
<plugin>
<g...
Thread Maven Version ranges - Release snapshot bug
Maven Version ranges - Release snapshot bugFor the ranges to work at all, you need to use the 2.0.0-beta-7 version of the maven release plugin. Many of our poms currently reference 2.0.0-beta-6 so the release process doesn't understand version ranges. But ev...
aop pom for CR8Paul why are you breaking people's builds? http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139298#4139298 Since the MC projects rely on jboss-aop to specify which versions of javassist, trove, qdox ...
org.jboss:jboss-common-core pomhttp://jira.jboss.com/jira/browse/JBCOMMON-44 I've changed a bit the pom of jboss-common-core. Can someone more maven savy confirm I didn't screw up? a) I've declared optional: apache-httpclient:commons-httpclient ...
Thread Getting dependency souces into local repository
Getting dependency souces into local repositoryI have found a way to do this using the mvn dependency:sources goal. More details are here: http://maven.apache.org/plugins/maven-dependency-plugin/sources-mojo.html I have updated the http://wiki.jboss.org/wiki/Wiki...
AS Components Bound to AS Release CycleMany AS Components are currently bound to the AS Release Cycle. ie: <dependency>
<groupId>org.jboss.jbossas</groupId>
<artifactId>jboss-as-aspects</artifactId>
<version>${proje...
EJB client launcherMy maven thirdparty build is not finding ejb3.client.ClientLauncher when building the testsuite. /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15-Maven-Thirdparty/trunk/testsuite/src/ma...
License linking in pomsIs it ok to put this URL to the lgpl in our poms? http://www.gnu.org/licenses/lgpl-2.1.txt Instead of the copy we currently use http://repository.jboss.org/licenses/lgpl.txt The maven convention is to point to the s...