« Return to Thread: [jira] Created: (MEVENIDE-614) war compiling into war class path recognition

[jira] Commented: (MEVENIDE-614) war compiling into war class path recognition

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View in Thread


    [ http://jira.codehaus.org/browse/MEVENIDE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128800#action_128800 ]

John Eichelsdorfer commented on MEVENIDE-614:
---------------------------------------------

I have been watching your changes and downloaded #359 and tried it.  I think think the new Mevenide loaded correctly, but I hope to have a chance to retest that later tonight.

I was still seeing red for classpath resolution.  It seemed the same net result in my environment, but I did not try to extract all classes manually as they are all built together in a chained build each time.  I used to have a bit more understanding on how warpath works, but I believe it unbundles the war for you and manages this aspect.   I am not sure that Netbeans notices where those classes are, however.  I need to do some looking around tonight if I can.   I sure wish the warpath developer was part of this rather then me, the novice.  I will see if I can get them involved as it would be a benefit to have the IDE work for AppFuse projects I think.




> war compiling into war class path recognition
> ---------------------------------------------
>
>                 Key: MEVENIDE-614
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-614
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>    Affects Versions: NB_3.1
>         Environment: Netbeans 6.1 Beta, Mevenide 3.1 Nightly from March 17,  AppFuse warpath plugin, Java 6.*,  Vista/XP
>            Reporter: John Eichelsdorfer
>            Assignee: Milos Kleint
>             Fix For: NB_3.1
>
>         Attachments: Demo.zip
>
>
> Wars fail to compile into each other using the AppFuse plugin within Netbeans embedded environment.  Switching from war targets to jar allows the projects to compile, but fail to create a correct end target.  Changing to jar targets once while having the pom  targets be jars rather then wars while pointing to an external maven will allow the first compile to work.  It is possible then to switch back to war files to compile, but classpaths then show up messed up.
> If I compile from a command line prompt using "mvn install" this works without error or any hitch.  It just fails embedded.
> I have attached an example of the problem.
> If AppFuse warpath plugin can not work,  please suggest a better working solution within Mevenide for unbundling war dependencies and including them in a target holding that dependency.

--
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

       

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

    http://xircles.codehaus.org/manage_email


 « Return to Thread: [jira] Created: (MEVENIDE-614) war compiling into war class path recognition