Jon Osborn (JIRA | 1 Oct 2008 03:01

[jira] Assigned: (MOJO-1223) com.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 not passed to appc


     [
http://jira.codehaus.org/browse/MOJO-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon Osborn reassigned MOJO-1223:
--------------------------------

    Assignee: Jon Osborn

> com.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 not passed to appc
> --------------------------------------------------------------------------------
>
>                 Key: MOJO-1223
>                 URL: http://jira.codehaus.org/browse/MOJO-1223
>             Project: Mojo
>          Issue Type: Bug
>          Components: weblogic
>         Environment: Windows, Weblogic 9.2.0, Plugin 2.9.1-SNAPSHOT
>            Reporter: Dennis Kieselhorst
>            Assignee: Jon Osborn
>
> I have to pass com.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 as a system property
because of a JDK QName issue (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6424960).
> AppcMojo:144 calls System.setProperty(
"com.sun.xml.namespace.QName.useCompatibleSerialVersionUID", "1.0" ); but it seems not to be
passed to appc:
> [INFO] Exception encountered during APPC processing
> Embedded error: weblogic.utils.compiler.ToolFailureException: javax.xml.namespace.QName;
local class incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class
serialVersionUID = -9120448754896609940 - with nested exception: [java.io.InvalidClassException:
(Continue reading)

Jon Osborn (JIRA | 1 Oct 2008 03:01

[jira] Commented: (MOJO-1194) weblogic:appc is not working with Weblogic 10.0


    [
http://jira.codehaus.org/browse/MOJO-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149451#action_149451
] 

Jon Osborn commented on MOJO-1194:
----------------------------------

Pls post your maven config so I can have a look.

> weblogic:appc is not working with Weblogic 10.0
> -----------------------------------------------
>
>                 Key: MOJO-1194
>                 URL: http://jira.codehaus.org/browse/MOJO-1194
>             Project: Mojo
>          Issue Type: Bug
>          Components: weblogic
>         Environment: Windows XP
> JDK 1.5.0
> BEA Weblogic 10.0 MP1
>            Reporter: Julien HENRY
>
> There are lots of NoClassDefFoundError.
> java.lang.NoClassDefFoundError: weblogic/utils/classloaders/GenericClassLoader
> then I've added wl-api.jar to the plugin calsspath
> then
> java.lang.NoClassDefFoundError: javax/xml/stream/XMLStreamException
> then I've added api.jar to the plugin classpath
> then
(Continue reading)

Jon Osborn (JIRA | 1 Oct 2008 03:03

[jira] Assigned: (MOJO-1221) NullPointerException if weblogic.home is not set


     [
http://jira.codehaus.org/browse/MOJO-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon Osborn reassigned MOJO-1221:
--------------------------------

    Assignee: Jon Osborn

> NullPointerException if weblogic.home is not set
> ------------------------------------------------
>
>                 Key: MOJO-1221
>                 URL: http://jira.codehaus.org/browse/MOJO-1221
>             Project: Mojo
>          Issue Type: Bug
>          Components: weblogic
>         Environment: Windows, WL 9.2, Plugin 2.9.1-SNAPSHOT
>            Reporter: Dennis Kieselhorst
>            Assignee: Jon Osborn
>         Attachments: npe-wl-home.patch
>
>
> [INFO] [weblogic:appc {execution: default}]
> [INFO]  Setting weblogic.home = null
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
(Continue reading)

Jon Osborn (JIRA | 1 Oct 2008 03:03

[jira] Commented: (MOJO-1221) NullPointerException if weblogic.home is not set


    [
http://jira.codehaus.org/browse/MOJO-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149453#action_149453
] 

Jon Osborn commented on MOJO-1221:
----------------------------------

This is true...I'll get the patch applied.

HOWEVER, appc probably won't work w/o weblogic.home configured anyway.

> NullPointerException if weblogic.home is not set
> ------------------------------------------------
>
>                 Key: MOJO-1221
>                 URL: http://jira.codehaus.org/browse/MOJO-1221
>             Project: Mojo
>          Issue Type: Bug
>          Components: weblogic
>         Environment: Windows, WL 9.2, Plugin 2.9.1-SNAPSHOT
>            Reporter: Dennis Kieselhorst
>            Assignee: Jon Osborn
>         Attachments: npe-wl-home.patch
>
>
> [INFO] [weblogic:appc {execution: default}]
> [INFO]  Setting weblogic.home = null
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
(Continue reading)

Jon Osborn (JIRA | 1 Oct 2008 03:03

[jira] Commented: (MOJO-1223) com.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 not passed to appc


    [
http://jira.codehaus.org/browse/MOJO-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149452#action_149452
] 

Jon Osborn commented on MOJO-1223:
----------------------------------

I will have a look. Please post your maven config here.

> com.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 not passed to appc
> --------------------------------------------------------------------------------
>
>                 Key: MOJO-1223
>                 URL: http://jira.codehaus.org/browse/MOJO-1223
>             Project: Mojo
>          Issue Type: Bug
>          Components: weblogic
>         Environment: Windows, Weblogic 9.2.0, Plugin 2.9.1-SNAPSHOT
>            Reporter: Dennis Kieselhorst
>            Assignee: Jon Osborn
>
> I have to pass com.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 as a system property
because of a JDK QName issue (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6424960).
> AppcMojo:144 calls System.setProperty(
"com.sun.xml.namespace.QName.useCompatibleSerialVersionUID", "1.0" ); but it seems not to be
passed to appc:
> [INFO] Exception encountered during APPC processing
> Embedded error: weblogic.utils.compiler.ToolFailureException: javax.xml.namespace.QName;
local class incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class
(Continue reading)

Jon Osborn (JIRA | 1 Oct 2008 03:05

[jira] Assigned: (MOJO-1194) weblogic:appc is not working with Weblogic 10.0


     [
http://jira.codehaus.org/browse/MOJO-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon Osborn reassigned MOJO-1194:
--------------------------------

    Assignee: Jon Osborn

> weblogic:appc is not working with Weblogic 10.0
> -----------------------------------------------
>
>                 Key: MOJO-1194
>                 URL: http://jira.codehaus.org/browse/MOJO-1194
>             Project: Mojo
>          Issue Type: Bug
>          Components: weblogic
>         Environment: Windows XP
> JDK 1.5.0
> BEA Weblogic 10.0 MP1
>            Reporter: Julien HENRY
>            Assignee: Jon Osborn
>
> There are lots of NoClassDefFoundError.
> java.lang.NoClassDefFoundError: weblogic/utils/classloaders/GenericClassLoader
> then I've added wl-api.jar to the plugin calsspath
> then
> java.lang.NoClassDefFoundError: javax/xml/stream/XMLStreamException
> then I've added api.jar to the plugin classpath
> then
(Continue reading)

Benjamin Bentmann | 1 Oct 2008 07:49

Re: JavaCC Maven Plugin at Geronimo

Jason Dillon wrote:

> Notice the ASTOpaqueString, ASTPlainString and ASTQuotedString, which 
> are defined in src/main/java/* ?  There are also classes of the same 
> name, the generated bits, in the target/generated-sources/jjtree output.

The Mojo plugin is currently collecting the output from both JJTree and 
JavaCC into "generated-source/javacc" and registeres this (and only 
this) directory as a compile source root with the Maven build.

In the light of http://www.jetbrains.net/jira/browse/IDEA-19177 I 
started to ask myself what were the compelling reasons to do so instead 
of registering "generated-source/jjtree" and "generated-source/javacc" 
as two independent source roots. Apart from possibly saving a few lines 
of code, I spontaneously don't see a necessity for the current approach. 
So I will try to change that such that IDEA hopefully works out of the 
box with the plugin.

Benjamin

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Julien HENRY (JIRA | 1 Oct 2008 09:33

[jira] Commented: (MOJO-1194) weblogic:appc is not working with Weblogic 10.0


    [
http://jira.codehaus.org/browse/MOJO-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149477#action_149477
] 

Julien HENRY commented on MOJO-1194:
------------------------------------

Hi,

Thanks for your interest. Since the day I reported the bug, I'm now using Oracle Weblogic 10.3. But I think
the problem is the same and I found a solution on a forum. Weblogic JARs are not easily hostable on Maven
repository because they are using there own location to find other dependencies.
Read comment #3 on this post: http://monduke.com/2007/08/29/maven-and-weblogicmbeanmaker-in-weblogic-910/

This guy is talking about "weblogic.Home.getHome() to get to the BEA installation directory and appends
the relative path's to various different jars it depends on"

So finally I made weblogic:appc working with this configuration:
{code:xml} 
        <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>weblogic-maven-plugin</artifactId>
                <version>2.9.0</version>
                <configuration>
                    <adminServerHostName>localhost</adminServerHostName>
                    <adminServerPort>7001</adminServerPort>
                    <adminServerProtocol>http</adminServerProtocol>
                    <userId>weblogic</userId>
                    <password>weblogic</password>
(Continue reading)

Kaare Nilsen (JIRA | 1 Oct 2008 10:49

[jira] Assigned: (MAPPASM-70) Appassembler does not create correct relative paths for snapshot dependencies


     [
http://jira.codehaus.org/browse/MAPPASM-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kaare Nilsen reassigned MAPPASM-70:
-----------------------------------

    Assignee: Kaare Nilsen

> Appassembler does not create correct relative paths for snapshot dependencies
> -----------------------------------------------------------------------------
>
>                 Key: MAPPASM-70
>                 URL: http://jira.codehaus.org/browse/MAPPASM-70
>             Project: Mojo AppAssembler Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0-beta-2
>         Environment: All
>            Reporter: Kaare Nilsen
>            Assignee: Kaare Nilsen
>             Fix For: 1.0
>
>
> When using snapshot dependencies the relative path for the dep is wrong. As shown in the example below :
> <dependency>
>         <groupId>org.springframework</groupId>
>         <artifactId>spring-orm</artifactId>
>         <version>2.5.6-20080930.010034-59</version>
>         <relativePath>org/springframework/spring-orm/2.5.6-20080930.010034-59/spring-orm-2.5.6-20080930.010034-59.jar</relativePath>
> </dependency>
(Continue reading)

Kaare Nilsen (JIRA | 1 Oct 2008 10:49

[jira] Created: (MAPPASM-70) Appassembler does not create correct relative paths for snapshot dependencies

Appassembler does not create correct relative paths for snapshot dependencies
-----------------------------------------------------------------------------

                 Key: MAPPASM-70
                 URL: http://jira.codehaus.org/browse/MAPPASM-70
             Project: Mojo AppAssembler Plugin
          Issue Type: Bug
    Affects Versions: 1.0-beta-2
         Environment: All
            Reporter: Kaare Nilsen
             Fix For: 1.0

When using snapshot dependencies the relative path for the dep is wrong. As shown in the example below :
<dependency>
        <groupId>org.springframework</groupId>
        <artifactId>spring-orm</artifactId>
        <version>2.5.6-20080930.010034-59</version>
        <relativePath>org/springframework/spring-orm/2.5.6-20080930.010034-59/spring-orm-2.5.6-20080930.010034-59.jar</relativePath>
</dependency>

This should be :
<dependency>
        <groupId>org.springframework</groupId>
        <artifactId>spring-orm</artifactId>
        <version>2.5.6-SNAPSHOT</version>
        <relativePath>org/springframework/spring-orm/2.5.6-SNAPSHOT/spring-orm-2.5.6-20080930.010034-59.jar</relativePath>
 </dependency>

Well.. from a release point of view we never should allow snapshot deps anyway, but it kind a ruins it during
development, so i guess we need to fix it :)
(Continue reading)


Gmane