Build broken
by Stan Silvert
Looks like somebody needs to put jboss-ha-client version 1.1.0.CR3 in
the Maven repo.
[java] [INFO]
------------------------------------------------------------------------
[java] [ERROR] BUILD ERROR
[java] [INFO]
------------------------------------------------------------------------
[java] [INFO] Failed to resolve artifact.
[java] Missing:
[java] ----------
[java] 1) org.jboss.cluster:jboss-ha-client:jar:1.1.0.CR3
[java] Try downloading the file manually from the project website.
[java] Then, install it using the command:
[java] mvn install:install-file -DgroupId=org.jboss.cluster
-DartifactId=jboss-ha-client -Dversion=1.1.0.CR3 -Dpa
ckaging=jar -Dfile=/path/to/file
[java] Alternatively, if you host your own repository you can
deploy the file there:
[java] mvn deploy:deploy-file -DgroupId=org.jboss.cluster
-DartifactId=jboss-ha-client -Dversion=1.1.0.CR3 -Dpack
aging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[java] Path to dependency:
[java] 1) org.jboss.jbossas:jboss-as-thirdparty:pom:5.0.0-SNAPSHOT
[java] 2) org.jboss.cluster:jboss-ha-client:jar:1.1.0.CR3
[java] ----------
[java] 1 required artifact is missing.
[java] for artifact:
[java] org.jboss.jbossas:jboss-as-thirdparty:pom:5.0.0-SNAPSHOT
[java] from the specified remote repositories:
[java] central (http://repo1.maven.org/maven2),
[java] repository.jboss.org (http://repository.jboss.org/maven2),
[java] snapshots.jboss.org (http://snapshots.jboss.org/maven2)
16 years, 4 months
Please commit using JIRA+descriptive comment
by Dimitris Andreadis
When committing, please do not forget to add a descriptive comment along with the JIRA
number, so you don't have to dig into fish eye & JIRA to find out what a particular commit
is about, while looking at svn log histories or hudson builds.
Thanks
/D
16 years, 4 months
jboss-beans.xml versus spring-beans.xml
by Adrian Brock
Since a number of users are complaining about us
trying to process WEB-INF/spring-beans.xml
as an MC -beans.xml file, even though
spring-beans.xml should be in WEB-INF/classes
I'm going to go through and change all our
-beans.xml files to end with -jboss-beans.xml
https://jira.jboss.org/jira/browse/JBAS-5803
e.g. ejb3-deployer-beans.xml becomes
ejb3-deployer-jboss-beans.xml
To try to keep the history of these files
I'll be moving them in the repository
along with seperate commits to the build files.
To try to keep the individual changes
as atomic as possible I'll be doing it project
by project in jboss-head.
Problems you might see:
1) I'll be doing the testsuite last, so
some of the overridden configs may not
work because it will be copying over the
wrong file until I've changed them.
2) If you are doing incremental builds
you might end up with both the old and
new file in your jboss image which
will surface as an attempt to deploy a bean twice.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
16 years, 5 months