|
Re: Creating a Ghost project? [message #1441546 is a reply to message #1441113] |
Thu, 09 October 2014 22:11 |
|
On 10/09/2014 05:43 AM, Harry Greijer wrote:
> Hi!
>
> I have a project "A" with its owns structure and I cant run it in
> weblogic in Eclipse.
> I can not change anything.
>
> Is it possible to create a "ghost project" "B" that links java classes
> and beans from project A.
> That "ghost project" "B" should build it the Eclipse way and all classes
> in its own location.
> Then I could easily add it to weblogic and debug it as is.
> So all source code should remain in project A but classfiles end up in
> project B.
>
> Is that possible?
> Strange question :)
Have you tried using this application as a JAR library to your ghost
project? I don't understand exactly what you mean by "I cannot change
anything."
|
|
|
|
Re: Creating a Ghost project? [message #1444283 is a reply to message #1443753] |
Mon, 13 October 2014 22:43 |
|
On 10/13/2014 01:06 AM, Harry Greijer wrote:
> I have tought about this jar fil solution. But I want to be able to
> change the source code and do hotdeploy.
>
> The structure of the project A is what it is and its politicaly
> imposible for me to change it.
> You know corporate decisions! :)
> I just have to find a easy way around the problem and use eclipse
> features to improve my work.
This is really nothing more than a Java question, but Eclipse can help
you work around it.
Assuming the application is distributed as a JAR or, if a package such
as Debian or RPM, you can nevertheless pull the JAR out from it, you
create your new project (B) and just use project A's JAR as a JAR
library to consume all the classes you want from it. Project B gets
built as a new deliverable, and happens to have the old deliverable
inside (it just doesn't use the main()).
Does this help?
|
|
|
Powered by
FUDForum. Page generated in 0.03409 seconds