-
1. Re: 2.0.0.Beta5 released
kabirkhan Oct 20, 2007 8:29 AM (in response to starksm64)I need a retroed jboss container jar in
http://repository.jboss.org/jboss/microcontainer14/2.0.0.Beta4/
But I get problemsKabir@KabirDell ~/sourcecontrol/microcontainer/container $ mvn -f pom-jdk14.xml clean install [INFO] Scanning for projects... Downloading: http://repo1.maven.org/maven2/org/jboss/microcontainer-jdk14/jboss-microcontainer-jdk14/2.0.0.Beta5/jboss-microcontainer-jdk14-2.0.0.Beta5.pom [WARNING] Unable to get resource 'org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14:pom:2.0.0.Beta5' from repository central (http://repo1.maven.org/maven2) [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. GroupId: org.jboss.microcontainer-jdk14 ArtifactId: jboss-microcontainer-jdk14 Version: 2.0.0.Beta5 Reason: Unable to download the artifact from any repository org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14:pom:2.0.0.Beta5 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14 for project: null:jboss-container-jdk14:jar:null at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:373) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:286) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) 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:324) 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-jdk14:jboss-microcontainer-jdk14 for project: null:jboss-container-jdk14:jar:null at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1198) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:697) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:431) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:195) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:523) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:455) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:359) ... 11 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14' not found in repository: Unable to download the artifact from any repository org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14:pom:2.0.0.Beta5 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:528) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1194) ... 17 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14:pom:2.0.0.Beta5 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:197) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:73) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:482) ... 18 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:308) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:185) ... 20 more [INFO] ------------------------------------------------------------------------ [INFO] Total time: < 1 second [INFO] Finished at: Sat Oct 20 13:29:33 BST 2007 [INFO] Final Memory: 1M/2M [INFO] ------------------------------------------------------------------------
-
2. Re: 2.0.0.Beta5 released
starksm64 Oct 20, 2007 12:03 PM (in response to starksm64)You mean from the 2.0.0.Beta5 tag?
https://svn.jboss.org/repos/jbossas/projects/microcontainer/tags/2.0.0.Beta5/
I did not update the pom-jdk14.xml so that will be one problem. What jars are we retroing when we do a release? -
3. Re: 2.0.0.Beta5 released
starksm64 Oct 20, 2007 12:27 PM (in response to starksm64)I updated the version in the poms and the build is failing due to out of date commons version being used. This is referring to the 2.2.1-SNAPSHOT which itself is a jdk5 artifact.
[INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure C:\home\svn\JBossMC\tags\2.0.0.Beta5\container\src\main\org\jboss\reflect\plugin s\introspection\IntrospectionTypeInfoFactoryImpl.java:[59,33] cannot find symbol symbol : class WeakTypeCache location: package org.jboss.util.collection
-
4. Re: 2.0.0.Beta5 released
kabirkhan Oct 20, 2007 12:33 PM (in response to starksm64)"scott.stark@jboss.org" wrote:
You mean from the 2.0.0.Beta5 tag?
https://svn.jboss.org/repos/jbossas/projects/microcontainer/tags/2.0.0.Beta5/
I did not update the pom-jdk14.xml so that will be one problem. What jars are we retroing when we do a release?
I only need the jar from the container/ project -
5. Re: 2.0.0.Beta5 released
starksm64 Oct 20, 2007 12:59 PM (in response to starksm64)These versions referrenced by the build/pom-jdk14.xml don't make sense for a retrod jar though, so what was the last version of the mc that was retrod?
<properties> <version.jboss.common.core>2.2.1-SNAPSHOT</version.jboss.common.core> <version.jbossxb>2.0.0.CR3</version.jbossxb> <version.osgi.r4.core>1.0</version.osgi.r4.core> <version.jboss.vfs>2.0.4.snapshot</version.jboss.vfs> <version.javassist>3.6-beta</version.javassist> <version.jaxb.api>2.0</version.jaxb.api> <version.jboss.aop>2.0.0-SNAPSHOT</version.jboss.aop> <version.jboss.common.logging.spi>2.0.5-SNAPSHOT</version.jboss.common.logging.spi> <version.jboss.classloading.spi>5.0.0-SNAPSHOT</version.jboss.classloading.spi> <version.org.jboss.test>1.0.4-SNAPSHOT</version.org.jboss.test> <version.junit>3.8.1</version.junit> <version.jboss.profiler.jvmti>1.0.0.CR5</version.jboss.profiler.jvmti> <version.ant.junit>1.7.0</version.ant.junit> <version.backport.concurrent>2.1.0.GA</version.backport.concurrent> <version.javax.management.jmxri>1.2.1</version.javax.management.jmxri> <version.org.jbossretro.rt>1.1.2</version.org.jbossretro.rt> </properties>
-
6. Re: 2.0.0.Beta5 released
alesj Oct 22, 2007 10:28 AM (in response to starksm64)"scott.stark@jboss.org" wrote:
I put out the 2.0.0.Beta5 release.
When are you moving this to AS5_trunk?<componentref name="jboss/microcontainer" version="2.0.0.Beta4"/>
-
7. Re: 2.0.0.Beta5 released
alesj Oct 22, 2007 10:34 AM (in response to starksm64)"alesj" wrote:
When are you moving this to AS5_trunk?
OK, build-thirdparty picked up the new version.
I can commit this change, along with other fixes that need to be done - e.g. MC annotation's package change, ... -
8. Re: 2.0.0.Beta5 released
starksm64 Oct 22, 2007 2:58 PM (in response to starksm64)It can be committed. The only issue was the retro version Kabir was looking for.