You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Todd Nine (JIRA)" <ji...@codehaus.org> on 2006/03/15 16:39:32 UTC

[jira] Created: (MEJB-7) Transitive Classpath not written to the manifest

Transitive Classpath not written to the manifest
------------------------------------------------

         Key: MEJB-7
         URL: http://jira.codehaus.org/browse/MEJB-7
     Project: Maven 2.x Ejb Plugin
        Type: Bug

    Reporter: Todd Nine


The transitive classpath of all dependencies from the dependencies in an EJB pom are not added to the MANIFEST.MF classpath. This causes the ejb to not deploy correctly.

Todd

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (MEJB-7) Transitive Classpath not written to the manifest

Posted by "Sam Wilson (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEJB-7?page=comments#action_78519 ] 
            
Sam Wilson commented on MEJB-7:
-------------------------------

That seems to solve the issue.

However, given that this is part of the spec, shouldn't this be the default behavior and not require this sort of archane override?

I went through the homepage for the plugin, the guides as well as the "Better Builds With Maven" book and found no reference to this property, which would be required for proper deployment in a compliant container. 

It would be nice to see this referenced in the documentation somewhere, or to have the default changed to something more appropriate (provided that won't cause other things to brake in a terrible way).

Thanks for the solution.

> Transitive Classpath not written to the manifest
> ------------------------------------------------
>
>                 Key: MEJB-7
>                 URL: http://jira.codehaus.org/browse/MEJB-7
>             Project: Maven 2.x Ejb Plugin
>          Issue Type: Bug
>            Reporter: Todd Nine
>
> The transitive classpath of all dependencies from the dependencies in an EJB pom are not added to the MANIFEST.MF classpath. This causes the ejb to not deploy correctly.
> Todd

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Closed: (MEJB-7) Transitive Classpath not written to the manifest

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MEJB-7?page=all ]

Dennis Lundberg closed MEJB-7.
------------------------------

         Assignee: Dennis Lundberg
       Resolution: Fixed
    Fix Version/s: 2.1

An entry has been added to the plugin's FAQ about this issue.
The default value for the configuration parameter has *not* been changed.

> Transitive Classpath not written to the manifest
> ------------------------------------------------
>
>                 Key: MEJB-7
>                 URL: http://jira.codehaus.org/browse/MEJB-7
>             Project: Maven 2.x Ejb Plugin
>          Issue Type: Bug
>            Reporter: Todd Nine
>         Assigned To: Dennis Lundberg
>             Fix For: 2.1
>
>
> The transitive classpath of all dependencies from the dependencies in an EJB pom are not added to the MANIFEST.MF classpath. This causes the ejb to not deploy correctly.
> Todd

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MEJB-7) Transitive Classpath not written to the manifest

Posted by "Mark Chesney (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEJB-7?page=comments#action_61994 ] 

Mark Chesney commented on MEJB-7:
---------------------------------

Have you configured the archive.manifest.addClasspath property?

		<plugins>
			<plugin>
				<artifactId>maven-ejb-plugin</artifactId>
				<configuration>
					<archive>
						<manifest>
							<addClasspath>true</addClasspath>
						</manifest>
					</archive>
				</configuration>
			</plugin>
		</plugins>

> Transitive Classpath not written to the manifest
> ------------------------------------------------
>
>          Key: MEJB-7
>          URL: http://jira.codehaus.org/browse/MEJB-7
>      Project: Maven 2.x Ejb Plugin
>         Type: Bug

>     Reporter: Todd Nine

>
>
> The transitive classpath of all dependencies from the dependencies in an EJB pom are not added to the MANIFEST.MF classpath. This causes the ejb to not deploy correctly.
> Todd

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira