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

[Design of JBoss Build System] - Re: Maven Version ranges - generateReleasePoms

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | e.g. you can see that during my testing I have been using some | local repositories to get artifacts. | It would be even better if it told you where it got the artifacts from i.e. some xml element that said junit.jar came from repository.jboss.org and also listed more of the plugins actually used with their versions and configurations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139824#4139824 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139824

18 years, 2 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Maven Version ranges - The version format

by alesj

"adrian(a)jboss.org" wrote : | However Maven doesn't use that scheme: | http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+... | instead it is | major.minor.micro-qualifier-build | | So our | jboss-5.0.0.Beta4 | should be under maven | jboss-5.0.0-Beta-4 | for the version ranges to work properly. Can't you hack this? e.g. first trying how maven wants it, then also try our own So that the old stuff would still work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139823#4139823 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139823

18 years, 2 months

1
0
0 / 0

[Design of JBoss Build System] - Maven Version ranges - generateReleasePoms

by adrian＠jboss.org

In 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> | <groupId>org.apache.maven.plugins</groupId> | <artifactId>maven-release-plugin</artifactId> | <version>2.0-beta-7</version> | <configuration> |  | | <tagBase>svn://localhost/project2/tags/</tagBase> | |  | | <generateReleasePoms>true</generateReleasePoms> | |  | <useReleaseProfile>false</useReleaseProfile> | |  | <arguments>-Prelease</arguments> | </configuration> | <inherited>true</inherited> | </plugin> | </plugins> | I think we should do this anyway even if we don't use version ranges. This captures all the information used to build the release including the user's ~/.m2/settings.xml relevant to the build e.g. you can see that during my testing I have been using some local repositories to get artifacts. | <?xml version="1.0" encoding="UTF-8"?><project> | <modelVersion>4.0.0</modelVersion> | <groupId>test</groupId> | <artifactId>project2</artifactId> | <name>Project2</name> | <version>1.0.0-Beta-5</version> | <description>Project2</description> | <url>http://www.jboss.org/project2</url> | <issueManagement> | <system>jira</system> | <url>http://jira.jboss.com/</url> | </issueManagement> | <licenses> | <license> | <name>lgpl</name> | <url>http://repository.jboss.com/licenses/lgpl.txt</url> | </license> | </licenses> | <scm> | <connection>svn://localhost/project2/tags/project2-1.0.0-Beta-5</connection> | <developerConnection>svn://localhost/project2/tags/project2-1.0.0-Beta-5</developerConnection> | </scm> | <organization> | <name>JBoss, a division of Red Hat, Inc.</name> | <url>http://www.jboss.org</url> | </organization> | <build> | <sourceDirectory>src/main</sourceDirectory> | <scriptSourceDirectory>src/main/scripts</scriptSourceDirectory> | <testSourceDirectory>src/tests</testSourceDirectory> | <outputDirectory>target/classes</outputDirectory> | <testOutputDirectory>target/test-classes</testOutputDirectory> | <resources> | <resource> | <directory>src/main/resources</directory> | </resource> | </resources> | <testResources> | <testResource> | <directory>src/test/resources</directory> | </testResource> | </testResources> | <directory>target</directory> | <finalName>project2</finalName> | <plugins> | <plugin> | <artifactId>maven-surefire-plugin</artifactId> | <version>2.4.1</version> | <configuration> | <redirectTestOutputToFile>true</redirectTestOutputToFile> | <includes> | <include>**/*TestCase.java</include> | </includes> | <useSystemClassLoader>true</useSystemClassLoader> | </configuration> | </plugin> | <plugin> | <artifactId>maven-release-plugin</artifactId> | <version>2.0-beta-7</version> | <inherited>true</inherited> | <configuration> | <tagBase>svn://localhost/project2/tags/</tagBase> | <generateReleasePoms>true</generateReleasePoms> | <useReleaseProfile>false</useReleaseProfile> | <arguments>-Prelease</arguments> | </configuration> | </plugin> | </plugins> | </build> | <repositories> | <repository> | <releases> | <enabled>false</enabled> | </releases> | <snapshots /> | <id>snapshots.jboss.org</id> | <url>file:///home/ejort/temp/snapshots</url> | </repository> | <repository> | <releases /> | <snapshots> | <enabled>false</enabled> | </snapshots> | <id>repository.jboss.org</id> | <url>http://repository.jboss.org/maven2</url> | </repository> | <repository> | <releases /> | <snapshots> | <enabled>false</enabled> | </snapshots> | <id>repository</id> | <url>file:///home/ejort/temp/maven-repository</url> | </repository> | <repository> | <snapshots> | <enabled>false</enabled> | </snapshots> | <id>central</id> | <name>Maven Repository Switchboard</name> | <url>http://repo1.maven.org/maven2</url> | </repository> | </repositories> | <pluginRepositories> | <pluginRepository> | <releases /> | <snapshots> | <enabled>false</enabled> | </snapshots> | <id>repository.jboss.org</id> | <url>http://repository.jboss.org/maven2</url> | </pluginRepository> | <pluginRepository> | <releases> | <updatePolicy>never</updatePolicy> | </releases> | <snapshots> | <enabled>false</enabled> | </snapshots> | <id>central</id> | <name>Maven Plugin Repository</name> | <url>http://repo1.maven.org/maven2</url> | </pluginRepository> | </pluginRepositories> | <dependencies> | <dependency> | <groupId>junit</groupId> | <artifactId>junit</artifactId> | <version>4.4</version> | <scope>test</scope> | </dependency> | <dependency> | <groupId>test</groupId> | <artifactId>project1</artifactId> | <version>1.0.0-Beta-1</version> | <scope>compile</scope> | </dependency> | </dependencies> | <reporting> | <outputDirectory>target/site</outputDirectory> | <plugins> | <plugin> | <artifactId>maven-javadoc-plugin</artifactId> | <version>2.2</version> | <configuration> | <links> | <link>http://java.sun.com/j2se/1.5.0/docs/api</link> | </links> | </configuration> | </plugin> | <plugin> | <artifactId>maven-project-info-reports-plugin</artifactId> | <version>2.0.1</version> | </plugin> | <plugin> | <artifactId>maven-surefire-report-plugin</artifactId> | <version>2.3</version> | <reportSets> | <reportSet> | <reports> | <report>report-only</report> | </reports> | </reportSet> | </reportSets> | </plugin> | <plugin> | <groupId>org.codehaus.mojo</groupId> | <artifactId>taglist-maven-plugin</artifactId> | <version>2.0</version> | </plugin> | </plugins> | </reporting> | <distributionManagement> | <repository> | <id>repository.jboss.org</id> | <url>file:///home/ejort/temp/maven-repository</url> | </repository> | <snapshotRepository> | <id>snapshots.jboss.org</id> | <name>JBoss Snapshot Repository</name> | <url>file:///home/ejort/temp/snapshots</url> | </snapshotRepository> | </distributionManagement> | <properties> | <maven.repository.root>/home/ejort/temp/maven-repository</maven.repository.root> | <jboss.repository.root>/home/ejort/temp/repository.jboss.org</jboss.repository.root> | </properties> | </project> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139822#4139822 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139822

18 years, 2 months

1
0
0 / 0

[Design of JBoss Build System] - Maven Version ranges - Release snapshot bug

by adrian＠jboss.org

For 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 even with the latest version there are bugs related to snapshots http://jira.codehaus.org/browse/MRELEASE-318 http://jira.codehaus.org/browse/MNG-3092 This shouldn't be issue if you have your ~/.m2/settings.xml exclude snapshots when doing releases???? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139821#4139821 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139821

18 years, 2 months

1
0
0 / 0

[Design of JBoss Build System] - Maven Version ranges - The version format

by adrian＠jboss.org

I'm in the process of testing Maven's version constraint handling. I'm going to use different threads to document each issue found First the version format: The way we are specifying versions is similar to how OSGi handles versions i.e. major.minor.micro.qualifier However Maven doesn't use that scheme: http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+... instead it is major.minor.micro-qualifier-build So our jboss-5.0.0.Beta4 should be under maven jboss-5.0.0-Beta-4 for the version ranges to work properly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139820#4139820 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139820

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Is JBVFS-2 resolved

by mstruk

Hmm ... I guess I was jumping to conclusions :) But the test really passes for me. What OS and java are you using? - marko View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139812#4139812 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139812

18 years, 2 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Move dependency management back into app server svn stru

by dimitris＠jboss.org

"wolfc" wrote : EJB 3 requires an electronic overview of all components used in JBoss AS 5.0.0.CR1. This is to make sure we build against the correct versions. Since Maven is currently the build system defacto it must be directly consumable by Maven. | | How you do this? I don't care. | Where you put this? I don't care. | | As long as the above requirements are met before the actual release of JBoss AS 5.0.0.CR1. So I can actually deliver something usable in that AS version. 1) Your mission is to deliver a working EJB3 implementation, not screw up the AS build. 2) EJB3 is only pseudo-independent as long as cyclical dependencies exist. It was a mistake to move EJB3 outside AS until this is resolved. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139811#4139811 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139811

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: PropertyReplaceTC failing in maven

by adrian＠jboss.org

"alesj" wrote : "adrian(a)jboss.org" wrote : What does mvn dependency:tree say is getting used? | It still says this: | - http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137369#4137369 | | I'll get a hold of Paul. ;-( What that your maven is broken, what I posted or something else? This is what I get. It shows classloading-vfs using MC beta11 | [INFO] snapshot org.jboss.cl:jboss-classloading:2.0.0-SNAPSHOT: checking for updates from snapshots.jboss.org | [INFO] [dependency:tree] | [INFO] org.jboss.cl:jboss-classloading-vfs:jar:2.0.0-SNAPSHOT | [INFO] +- junit:junit:jar:4.4:test | [INFO] +- org.jboss:jboss-vfs:jar:2.0.0.Beta7:compile | [INFO] +- org.jboss.microcontainer:jboss-kernel:jar:2.0.0.Beta11:compile | [INFO] | \- org.jboss.microcontainer:jboss-dependency:jar:2.0.0.Beta11:compile | [INFO] | +- org.jboss:jboss-reflect:jar:2.0.0.Beta12:compile | [INFO] | \- org.jboss:jboss-mdr:jar:2.0.0.Beta12:compile | [INFO] +- jboss:jboss-common-logging-log4j:jar:2.0.4.GA:test | [INFO] | \- log4j:log4j:jar:1.2.14:test | [INFO] +- org.jboss:jboss-test:jar:1.0.5.GA:test | [INFO] +- org.jboss.man:jboss-managed:jar:2.0.0.Beta12:compile | [INFO] | \- org.jboss.man:jboss-metatype:jar:2.0.0.Beta12:compile | [INFO] +- org.jboss:jbossxb:jar:2.0.0.CR7:compile | [INFO] | +- apache-xerces:xercesImpl:jar:2.9.1:compile | [INFO] | +- wutka-dtdparser:dtdparser121:jar:1.2.1:compile | [INFO] | +- javax.activation:activation:jar:1.0.2:compile | [INFO] | \- javax.xml.bind:jaxb-api:jar:2.1:compile | [INFO] | +- javax.xml.stream:stax-api:jar:1.0-2:compile | [INFO] | \- (javax.activation:activation:jar:1.1:compile - omitted for conflict with 1.0.2) | [INFO] \- org.jboss.cl:jboss-classloading:jar:2.0.0-SNAPSHOT:compile | [INFO] +- (org.jboss.microcontainer:jboss-dependency:jar:2.0.0.Beta11:compile - omitted for duplicate) | [INFO] \- org.jboss.cl:jboss-classloader:jar:2.0.0-SNAPSHOT:compile | [INFO] +- org.jboss:jboss-classloading-spi:jar:5.0.0.Beta4:compile | [INFO] +- org.jboss:jboss-common-core:jar:2.2.3.GA:compile | [INFO] \- jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile | and all the tests pass: | Results : | | Tests run: 88, Failures: 0, Errors: 0, Skipped: 0 | | [INFO] [jar:jar] | [INFO] Building jar: /home/ejort/jboss-cl/classloading-vfs/target/jboss-classloading-vfs.jar | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139810#4139810 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139810

18 years, 2 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Move dependency management back into app server svn stru

by dimitris＠jboss.org

"ALRubinger" wrote : "dimitris(a)jboss.org" wrote : After the last call we had, I'm even more convinced that the component-matrix pom is a bad idea. | | The POM itself? Or its external location? | Having the AS pom.xml essentially outside the project. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139809#4139809 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139809

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Parsing more than one file

by adrian＠jboss.org

"alesj" wrote : "adrian(a)jboss.org" wrote : | | Again these are implementation details i.e. not requirements for CR1 | | | But I can keep my 'parseMultipleFiles' hook? | | If you like, but provide a way to do what I said above i.e. create multiple attachments for each file which should be the usual implementation when not throwing an error because it is not supported. e.g. you can't have two web.xmls View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139808#4139808 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139808

18 years, 2 months

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