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

[Design of JBoss Build System] - Re: maven-resources-plugin problem

by vickyk

Also noticed that this does not contain any repository http://ibiblio.lsu.edu/main/pub/packages/maven2 I have pom.xml with <pluginRepository> | <id>central</id> | <name>LSU maven2 mirror</name> | <url>http://ibiblio.lsu.edu/main/pub/packages/maven2</url> | <layout>default</layout> | <snapshots> | <enabled>false</enabled> | <updatePolicy>never</updatePolicy> | </snapshots> | </pluginRepository> Not sure if this is the problem ... Strange I was able to install,package an hour back , can't figure what changes broke it . View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063711#4063711 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063711

18 years, 9 months

1
0
0 / 0

[Design of JBoss Build System] - Re: maven-resources-plugin problem

by vickyk

C:\svn\jboss-jca\core>mvn install -e | + Error stacktraces are turned on. | [INFO] Scanning for projects... | [INFO] ------------------------------------------------------------------------- | --- | [INFO] Building JBoss JCA Core | [INFO] task-segment: [install] | [INFO] ------------------------------------------------------------------------- | --- | [INFO] ------------------------------------------------------------------------- | --- | [ERROR] BUILD ERROR | [INFO] ------------------------------------------------------------------------- | --- | [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not exi | st or no valid version could be found | [INFO] ------------------------------------------------------------------------- | --- | [INFO] Trace | org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.m | aven.plugins:maven-resources-plugin' does not exist or no valid version could be | found | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa | ultLifecycleExecutor.java:1247) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor | (DefaultLifecycleExecutor.java:1483) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForP | ackaging(DefaultLifecycleExecutor.java:979) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycl | eMappings(DefaultLifecycleExecutor.java:943) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau | ltLifecycleExecutor.java:450) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan | dleFailures(DefaultLifecycleExecutor.java:303) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen | ts(DefaultLifecycleExecutor.java:270) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi | fecycleExecutor.java:139) | at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) | at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) | at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. | java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces | sorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | 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.plugin.version.PluginVersionNotFoundException: The p | lugin 'org.apache.maven.plugins:maven-resources-plugin' does not exist or no val | id version could be found | at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePl | uginVersion(DefaultPluginVersionManager.java:225) | at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePl | uginVersion(DefaultPluginVersionManager.java:87) | at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlug | inManager.java:160) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa | ultLifecycleExecutor.java:1218) | ... 18 more | [INFO] ------------------------------------------------------------------------- | --- | [INFO] Total time: < 1 second | [INFO] Finished at: Fri Jul 13 01:18:31 IST 2007 | [INFO] Final Memory: 1M/2M | [INFO] ------------------------------------------------------------------------- | --- | I am too hit by the same error . Few moment back I was able to run it , I don't know what has happened suddenly :( I am in process of Mavenizing the JCA/MC stuff which is yet not checked in the svn . View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063707#4063707 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063707

18 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MAVEN: build change

by Kevin.Conner＠jboss.com

"adrian(a)jboss.org" wrote : Call the tag OLD_DEPLOYERS or something like that. Okay, that's done. It looks like the revision was actually 63676. The deployers project has now been removed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063688#4063688 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063688

18 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MAVEN: build change

by adrian＠jboss.org

Sorry, I've uncommitted changes I don't want to merge yet. ;-) Call the tag OLD_DEPLOYERS or something like that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063680#4063680 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063680

18 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MAVEN: build change

by Kevin.Conner＠jboss.com

"adrian(a)jboss.org" wrote : Ok, if you tag it first, so it is easy to find. It looks as if the changes were made in revision 63690, so I'll tag revision 63689. Any preference for a name? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063677#4063677 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063677

18 years, 9 months

1
0
0 / 0

[Design of POJO Server] - Re: New VFSClassLoader is nearly ready for JBoss Head

by adrian＠jboss.org

Anyway the plan is to do some more testing over the weekend then commit it. You can swap between the old and the new classloader by changing config in the bootstrap beans xml. Once it's in, it should then just be a case of adding the extra processing to handle the OSGi rules. "just" he says :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063676#4063676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063676

18 years, 9 months

1
0
0 / 0

[Design of JBoss ESB] - Re: JMSHeader fields

by beve

anonymous wrote : The current code seems to obtain it via the configuration file. Best to stick with that for now IMO. Configuration it is then. Should I rename JmsRouterUnitTest to JmsRouterIntegrationTest? Daniel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063672#4063672 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063672

18 years, 9 months

1
0
0 / 0

[Design of POJO Server] - New VFSClassLoader is nearly ready for JBoss Head

by adrian＠jboss.org

Before you get excited, this is not committed yet and its only using the old rules with a hacky deployer that converts LoaderRepositoryConfig to ClassLoaderMetaData It actually works pretty well once I got over two stupid problems: RESOURCE FILTERING I've got some tidying up to do here I realised once I'd integrated it that the way the class filtering was working doesn't work for resources. e.g. org.jboss.xxx.notpublic.PrivateClass won't be exposed if only org.jboss.xxx is exported as a package BUT org.jboss.xxx.some-resource.xml should be exported. The dot in some-resource.xml confused it because it thought some-resource is a package and xml the file :-) VFS BUG I also rewrote the exportAll package determination. There's a horrible bug in the VFS where if you do | URI uri = file.toURI(); | VirtualFile root = VFS.getRoot(uri); | it gives you back a virtual file that's has a "pathName" for jar uris. The path name is the name of the jar. Actually, the new code is a lot cleaner. :-) MORE TESTING I also broke at least one test. In a good way:-) This test I wrote earlier this week is failing because the new VFSClassLoader throws the correct SecurityException (unlike the UCL) | 20:32:22,616 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta3 (build: SVNTag=JBoss_5_0_0_Beta3 date=200707101429)] Started in 40s:829ms | 20:32:58,247 INFO [MainDeployer] deploy, url=file:/home/ejort/jboss-head/testsuite/output/lib/test-java-class-isolation.sar | 20:32:58,283 WARN [ClassLoaderManager] Unexpected error during load of:java.org.jboss.test.Test | java.lang.SecurityException: Prohibited package name: java.org.jboss.test | at java.lang.ClassLoader.preDefineClass(ClassLoader.java:479) | at java.lang.ClassLoader.defineClass(ClassLoader.java:614) | at org.jboss.classloader.spi.base.BaseClassLoader.access$2(BaseClassLoader.java:1) | at org.jboss.classloader.spi.base.BaseClassLoader$1.run(BaseClassLoader.java:271) | at org.jboss.classloader.spi.base.BaseClassLoader$1.run(BaseClassLoader.java:1) | at java.security.AccessController.doPrivileged(Native Method) | at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:245) | at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:218) | at org.jboss.classloader.spi.base.BaseDelegateLoader.loadClass(BaseDelegateLoader.java:75) | at org.jboss.classloader.spi.base.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:449) | at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:251) | at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:145) | at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:191) | at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:766) | at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:479) | at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:159) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at org.jboss.test.isolation.mbean.JavaClassIsolation.test(JavaClassIsolation.java:51) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063670#4063670 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063670

18 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MAVEN: build change

by Kevin.Conner＠jboss.com

I have checked in the modified poms and regenerated the eclipse project/classpath files. Can someone please check and see if anything is amiss? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063669#4063669 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063669

18 years, 9 months

1
0
0 / 0

[Design of Security on JBoss] - Security Configuration for JBoss 5

by anil.saldhana＠jboss.com

With the future changes for trust, JASPI, audit etc being made into the security configuration, I am contemplating if it is the right time to adopt JAXB2 for JBoss5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063663#4063663 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063663

18 years, 9 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 July 2007