You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ol (JIRA)" <ji...@codehaus.org> on 2011/05/16 13:22:22 UTC
[jira] Commented: (MECLIPSE-689) The WTP configuration does not
work for weblogic
[ http://jira.codehaus.org/browse/MECLIPSE-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267126#action_267126 ]
ol commented on MECLIPSE-689:
-----------------------------
In fact the maven-eclipse-plugin configuration inherits from a master configuration... so the configuration in the ear component is
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.8</version>
<configuration>
<additionalProjectnatures>
<projectnature>org.eclipse.jdt.core.javanature</projectnature>
<projectnature>net.sf.eclipsecs.core.CheckstyleNature</projectnature>
</additionalProjectnatures>
<additionalBuildcommands>
<buildcommand>org.eclipse.jdt.core.javabuilder</buildcommand>
<buildcommand>net.sf.eclipsecs.core.CheckstyleBuilder</buildcommand>
</additionalBuildcommands>
<downloadSources>true</downloadSources>
<wtpversion>2.0</wtpversion>
<wtpapplicationxml>true</wtpapplicationxml>
</configuration>
</plugin>
> The WTP configuration does not work for weblogic
> ------------------------------------------------
>
> Key: MECLIPSE-689
> URL: http://jira.codehaus.org/browse/MECLIPSE-689
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Environment: windows, maven 2.2.1
> Reporter: ol
>
> A problem occurs when doing the eclipse goal on a project, trying to transform it into a WTP Project.
> The maven-eclipse-plugin is configure like this in the EJB:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-eclipse-plugin</artifactId>
> <version>2.8</version>
> <configuration>
> <additionalProjectnatures>
> <projectnature>org.eclipse.jdt.core.javanature</projectnature>
> <projectnature>net.sf.eclipsecs.core.CheckstyleNature</projectnature>
> </additionalProjectnatures>
> <additionalBuildcommands>
> <buildcommand>org.eclipse.jdt.core.javabuilder</buildcommand>
> <buildcommand>net.sf.eclipsecs.core.CheckstyleBuilder</buildcommand>
> </additionalBuildcommands>
> <downloadSources>true</downloadSources>
> <wtpversion>2.0</wtpversion>
> </configuration>
> </plugin>
> And in the ear:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-eclipse-plugin</artifactId>
> <version>2.8</version>
> <configuration>
> <wtpapplicationxml>true</wtpapplicationxml>
> </configuration>
> </plugin>
> I found an issue in the class
> http://www.jarvana.com/jarvana/view/org/apache/maven/plugins/maven-eclipse-plugin/2.8/maven-eclipse-plugin-2.8-sources.jar!/org/apache/maven/plugin/eclipse/writers/wtp/EclipseWtpApplicationXMLWriter.java?format=ok
> The method createNewApplicationXml() contains this code:
> if ( this.config.getWorkspaceConfiguration().getWebsphereVersion() != null )
> {
> locationAttribute = EclipseWtpApplicationXMLWriter.XSI_SCHEMA_LOCATION;
> }
> else
> {
> locationAttribute = EclipseWtpApplicationXMLWriter.XMLNS_SCHEMA_LOCATION;
> }
> It's done for wepsphere ... but it should also be done for Weblogic (the weblogic version 10.3 that we use also needs this namespace). Without this, WTP can not deploy the ear.
--
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