[Design of JBoss Build System] - assembly manifest entries
by scott.stark＠jboss.org
Why doesn't the assembly plugin support the same manifest configuration as the jar plugin? The docs for the assembly plugin refer to the jar plugin for manfiest info, but the following does not work:
| <plugin>
|
| <groupId>org.apache.maven.plugins</groupId>
|
| <artifactId>maven-assembly-plugin</artifactId>
|
| <version>2.1</version>
|
| <executions>
|
| <execution>
|
| <phase>package</phase>
|
| <goals>
|
| <goal>attached</goal>
|
| </goals>
|
| </execution>
|
| </executions>
|
| <configuration>
| <archive>
| <manifest>
| <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
| <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
| </manifest>
| </archive>
| <descriptors>
|
| <descriptor>assembly/bin.xml</descriptor>
|
| <descriptor>assembly/sources.xml</descriptor>
|
| </descriptors>
|
| </configuration>
|
| <inherited>false</inherited>
|
| </plugin>
|
| [INFO] ------------------------------------------------------------------------
| [ERROR] BUILD ERROR
| [INFO] ------------------------------------------------------------------------
| [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-assembly-plugin:2.1
|
|
|
| Cause: Cannot find setter nor field in org.apache.maven.archiver.ManifestConfiguration for 'addDefaultSpecificationEntries'
| [INFO] ------------------------------------------------------------------------
| [INFO] For more information, run Maven with the -e switch
| [INFO] ------------------------------------------------------------------------
| [INFO] Total time: 2 seconds
| [INFO] Finished at: Sat Dec 15 08:45:45 PST 2007
| [INFO] Final Memory: 21M/293M
| [INFO] ------------------------------------------------------------------------
| [starksm@succubus security-jboss-sx]$
|
|
why doesn't this work?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113170#4113170
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113170
18 years, 3 months
[Design of JBoss Build System] - NPE unless clean done first
by scott.stark＠jboss.org
I was seeing this error until I did a clean of the mc project:
| [INFO] Installing /home/svn/JBossMC/jbossmc/deployers-structure-spi/target/jboss-deployers-structure-spi-tests.jar to /home/svn/repository.jboss.com/maven2/org/jboss/microcontainer/jboss-deployers-structure-spi/2.0.0-SNAPSHOT/jboss-deployers-structure-spi-2.0.0-SNAPSHOT-tests.jar
| [INFO] ----------------------------------------------------------------------------
| [INFO] Building JBoss Deployers SPI
| [INFO] task-segment: [install]
| [INFO] ----------------------------------------------------------------------------
| [INFO] [resources:resources]
| [INFO] Using default encoding to copy filtered resources.
| [INFO] [compiler:compile]
| [INFO] Nothing to compile - all classes are up to date
| [INFO] [resources:testResources]
| [INFO] Using default encoding to copy filtered resources.
| [INFO] [compiler:testCompile]
| [INFO] Nothing to compile - all classes are up to date
| [INFO] [surefire:test]
| [INFO] ------------------------------------------------------------------------
| [ERROR] FATAL ERROR
| [INFO] ------------------------------------------------------------------------
| [INFO] null
| [INFO] ------------------------------------------------------------------------
| [INFO] Trace
| java.lang.NullPointerException
| at org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBooter(SurefirePlugin.java:594)
| at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:391)
| at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
| at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
| at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
| at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
| 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: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)
| [INFO] ------------------------------------------------------------------------
| [INFO] Total time: 1 minute 11 seconds
| [INFO] Finished at: Sat Dec 15 08:18:37 PST 2007
| [INFO] Final Memory: 33M/330M
| [INFO] ------------------------------------------------------------------------
|
Don't know why the project gets into such a state.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113164#4113164
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113164
18 years, 3 months
[Design of JBoss Web Services] - JBWS-1858 + JBWS-1797: when to generate wsdl?
by alessio.soldano＠jboss.com
I'm analyzing the http://jira.jboss.org/jira/browse/JBWS-1858 which is related to JBWS-1797. The main concern is generating and exposing the wsdl contract after the eventual servlet context-param properties have been read and the metadata has changed accordingly. As a matter of fact they can influence the wsdl (.NET friendly Endpoint...).
Actually the wsdl creation is triggered during the create phase of the UnifiedMetaDataDeploymentAspect; either a new wsdl or the user provided one is selected, then the PublishContractDeploymentAspect publishes it. The new wsdl creation could be performed at some later stage, as far as I can see this would imply running the PublishContractDeploymentAspect and EagerInitializeDeploymentAspect later too, since they rely on the WSDLDefinition.
This however is not going to solve the JBWS-1797 with AS42: currently the EndpointServlet gets the context-params from the its context during the first call to the endpoint, however at that time the endpoint has already been started (at the end of the deployment, by the EndpointLifeCycleDeploymentAspect).
Thus according to me the main point here is not moving the wsdl generation later, it's instead reading the servlet context-params earlier, during the deployment. Of course we could do both the changes, but having those params available (for example as properties in the DeploymentInfo) before the UMDM is generated would be enough (and is required before the EndpointLifeCycleDeploymentAspect is run).
What do you think about this?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113145#4113145
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113145
18 years, 3 months
[Design of Security on JBoss] - Re: ant tests-jacc-security
by scott.stark＠jboss.org
We need to convert the jacc services to beans so that the DelegatingPolicy.instance can be retrieved as the JaccPolicyProvider bean using a factory:
| <deployment xmlns="urn:jboss:bean-deployer:2.0">
| <bean name="JaccPolicyProvider"
| class="org.jboss.security.jacc.DelegatingPolicy">
| <constructor factoryMethod="getInstance"
| factoryClass="org.jboss.security.jacc.DelegatingPolicy"/>
| </bean>
|
| <bean class="org.jboss.security.jacc.SecurityService"
| name="JaccSecurityService">
| <property name="mbeanServer"><inject bean="JMXKernel" property="mbeanServer"/></property>
| <property name="policy"><inject bean="JaccPolicyProvider" property="policy"/></property>
| </bean>
| </deployment>
|
The SecurityService needs to be pojoized to support this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113116#4113116
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113116
18 years, 3 months
[Design of POJO Server] - Re: BSH script from client
by alesj
"scott.stark(a)jboss.org" wrote : I guess so. Add a testcase to the mc project.
Done (but not yet commited).
But only root.bsh gets picked up, as your example did.
If it's like as it is in interceptors-beans.sar/jmx/interceptors/scripts/myscript.bsh, then it's not picked up, since jmx directory is not recognized.
Structure:
| - nmd.jar
| - jmx
| - interceptors
| - scripts
| - myscript.bsh
| - META-INF
| - root.bsh
|
Log:
| org.jboss.test.deployers.vfs.deployer.nonmetadata.test.MockBshDeployerTestCase
| 0 DEBUG [MockBshDeployerTestCase] ==== Starting testBshNonMetadataDeploy ====
| 31 DEBUG [VFSStructuralDeployersImpl] Added structure deployer org.jboss.deployers.vfs.plugins.structure.jar.JARStructure@911f71
| 47 DEBUG [VFSStructuralDeployersImpl] Added structure deployer org.jboss.deployers.vfs.plugins.structure.file.FileStructure@1eec612
| 78 DEBUG [DeployersImpl] Added stage Not Installed before null
| 78 DEBUG [DeployersImpl] Added stage Parse before ControllerState@84abc9{PreInstall}
| 78 DEBUG [DeployersImpl] Added stage Describe before ControllerState@84abc9{PreInstall}
| 78 DEBUG [DeployersImpl] Added stage ClassLoader before ControllerState@84abc9{PreInstall}
| 78 DEBUG [DeployersImpl] Added stage PostClassLoader before ControllerState@84abc9{PreInstall}
| 78 DEBUG [DeployersImpl] Added stage Real before ControllerState@84abc9{PreInstall}
| 78 DEBUG [DeployersImpl] Added stage Installed before ControllerState@84abc9{PreInstall}
| 109 DEBUG [DeployersImpl] Added deployer org.jboss.test.deployers.vfs.deployer.nonmetadata.support.MockBshDeployer@bfbdb0 for stage Parse
| org.jboss.test.deployers.vfs.deployer.nonmetadata.support.MockBshDeployer@bfbdb0{inputs=[] outputs=[org.jboss.test.deployers.vfs.deployer.nonmetadata.support.BshScript]}
|
| 188 DEBUG [MainDeployerImpl] Add deployment: vfsfile:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/
| 188 TRACE [VFSStructuralDeployersImpl] Determining structure for nmd.jar deployers=[org.jboss.deployers.vfs.plugins.structure.jar.JARStructure@911f71, org.jboss.deployers.vfs.plugins.structure.file.FileStructure@1eec612]
| 234 TRACE [JARStructure] Not using metadata path META-INF for nmd.jar reason: File does not exist: C:\projects\microcontainer\deployers-vfs\target\tests-classes\nonmetadata\nmd.jar\META-INF
| 234 TRACE [JARStructure] Added context ContextInfoImpl{path= metaData=[] classPath=null} from nmd.jar
| 234 DEBUG [VFSUtils] Can't find manifest for nmd.jar
| 234 TRACE [JARStructure] Added classpath entry for nmd.jar from FileHandler(a)3541984[path=nmd.jar context=file:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata real=file:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/]
| 250 TRACE [VFSStructuralDeployersImpl] Determining structure for jmx deployers=[org.jboss.deployers.vfs.plugins.structure.jar.JARStructure@911f71, org.jboss.deployers.vfs.plugins.structure.file.FileStructure@1eec612]
| 266 TRACE [JARStructure] ... no - doesn't look like a jar and no META-INF subdirectory.
| 266 TRACE [JARStructure] Not recognised: jmx
| 266 TRACE [FileStructure] ... no - not a file.
| 266 TRACE [FileStructure] Not recognised: jmx
| 266 TRACE [VFSStructuralDeployersImpl] jmx not recognised
| 266 TRACE [VFSStructuralDeployersImpl] Determining structure for root.bsh deployers=[org.jboss.deployers.vfs.plugins.structure.jar.JARStructure@911f71, org.jboss.deployers.vfs.plugins.structure.file.FileStructure@1eec612]
| 266 TRACE [JARStructure] ... no - not a directory or an archive.
| 266 TRACE [JARStructure] Not recognised: root.bsh
| 266 TRACE [FileStructure] FileHandler(a)7051261[path=nmd.jar/root.bsh context=file:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata real=file:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/root.bsh] is a leaf
| 266 TRACE [FileStructure] ... ok - not a top level file but it is a known name
| 266 TRACE [FileStructure] Added context ContextInfoImpl{path= metaData=[] classPath=null} from root.bsh
| 266 TRACE [FileStructure] FileHandler(a)7051261[path=nmd.jar/root.bsh context=file:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata real=file:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/root.bsh] isFile: true
| 281 TRACE [FileStructure] Recognised: root.bsh
| 281 TRACE [VFSStructuralDeployersImpl] root.bsh recognised by org.jboss.deployers.vfs.plugins.structure.file.FileStructure@1eec612
| 281 TRACE [JARStructure] Recognised: nmd.jar
| 281 TRACE [VFSStructuralDeployersImpl] nmd.jar recognised by org.jboss.deployers.vfs.plugins.structure.jar.JARStructure@911f71
| 281 TRACE [VFSStructureBuilder] Populating deployment vfsfile:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/ metaData=StructureMetaDataImpl{contexts=[ContextInfoImpl{path= metaData=[] classPath=[ClassPathEntryImpl{path=}]}, ContextInfoImpl{path=root.bsh metaData=[] classPath=null}]}
| 297 TRACE [VFSStructureBuilder] Apply context: vfsfile:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/ ContextInfoImpl{path= metaData=[] classPath=[ClassPathEntryImpl{path=}]}
| 297 TRACE [VFSStructureBuilder] Resolving classpath entry ClassPathEntryImpl{path=} for vfsfile:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/
| 313 TRACE [AbstractVFSDeploymentContext] ClassPath for nmd.jar is nmd.jar
| 313 TRACE [VFSStructureBuilder] Populating Context vfsfile:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/ metaData=StructureMetaDataImpl{contexts=[ContextInfoImpl{path= metaData=[] classPath=[ClassPathEntryImpl{path=}]}, ContextInfoImpl{path=root.bsh metaData=[] classPath=null}]}
| 313 TRACE [VFSStructureBuilder] Apply context: vfsfile:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/root.bsh ContextInfoImpl{path=root.bsh metaData=[] classPath=null}
| 313 TRACE [VFSStructureBuilder] Populating Context vfsfile:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/root.bsh metaData=StructureMetaDataImpl{contexts=[ContextInfoImpl{path= metaData=[] classPath=null}]}
| 313 DEBUG [MainDeployerImpl] Scheduling deployment: vfsfile:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/ parent=null
| 328 DEBUG [MainDeployerImpl] Scheduling deployment: vfsfile:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/root.bsh parent=AbstractVFSDeploymentContext@7254922{vfsfile:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/}
| 344 TRACE [DeployersImpl] Deployers for Not Installed []
| 344 TRACE [DeployersImpl] Deployers for Not Installed []
| 344 DEBUG [DeployersImpl] Deploying vfsfile:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/
| 344 TRACE [DeployersImpl] Deployers for Parse [org.jboss.test.deployers.vfs.deployer.nonmetadata.support.MockBshDeployer@bfbdb0]
| 359 TRACE [DeployersImpl] Deployers for Describe []
| 359 TRACE [DeployersImpl] Deployers for ClassLoader []
| 359 TRACE [DeployersImpl] Deployers for PostClassLoader []
| 359 TRACE [DeployersImpl] Deployers for Real []
| 359 TRACE [DeployersImpl] Deployers for PreInstall []
| 359 TRACE [DeployersImpl] Deployers for Described []
| 359 TRACE [DeployersImpl] Deployers for Instantiated []
| 359 TRACE [DeployersImpl] Deployers for Configured []
| 359 TRACE [DeployersImpl] Deployers for Create []
| 359 TRACE [DeployersImpl] Deployers for Start []
| 359 TRACE [DeployersImpl] Deployers for Installed []
| 359 DEBUG [DeployersImpl] Fully Deployed vfsfile:/C:/projects/microcontainer/deployers-vfs/target/tests-classes/nonmetadata/nmd.jar/
| 375 DEBUG [MockBshDeployerTestCase] testBshNonMetadataDeploy took 375ms
| 375 DEBUG [MockBshDeployerTestCase] ==== Stopping testBshNonMetadataDeploy ====
|
| Process finished with exit code 0
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113115#4113115
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113115
18 years, 3 months