|
| Re: packaging problem [message #15823 is a reply to message #15801] |
Thu, 13 November 2008 16:22   |
 Abel Mui
Messages: 247
Registered: July 2009 |
Senior Member |
|
|
Hello Andrei,
At this point, you can try closing the project in the workspace. This way,
the ones in the local or remote repository will be used.
For the longer term, you might like to open a ticket in bugzilla for
better supporting this scenario when resolving from the workspace.
Let us know if this worked!
Andrei Ivanov wrote:
> Hello,
> I'm using Q4E 0.8.0 with Eclipse 3.4.1 and I'm having a packaging
> problem...
> I have 2 modules, 'api' and 'model' using JDK 1.5 and retrotranslator
> activated.
> These seem to be fine, the JDK 1.4 artifacts are being created and
> installed in the local repository (using 'Locally install artifact').
> Another module, 'portal' depends on these 2 modules and specifies the 'j4'
> classifier for them.
> AFAIS, when running 'Package artifact' from Eclipse, the JDK 1.5 modules
> are being used and the 'j4' classifier is being added to them(which
> confused me and made me think at first the retrotranslator wasn't working).
> When using Maven from the command line, the proper jars are used.
> I suppose the problem comes from the fact that Q4E detects that the
> projects of the first 2 modules are present in the workspace and uses
> them...
> Is there anything I can do?
|
|
|
|
| Re: packaging problem [message #567960 is a reply to message #15801] |
Thu, 13 November 2008 16:22 |
Abel Mui
Messages: 247
Registered: July 2009 |
Senior Member |
|
|
Hello Andrei,
At this point, you can try closing the project in the workspace. This way,
the ones in the local or remote repository will be used.
For the longer term, you might like to open a ticket in bugzilla for
better supporting this scenario when resolving from the workspace.
Let us know if this worked!
Andrei Ivanov wrote:
> Hello,
> I'm using Q4E 0.8.0 with Eclipse 3.4.1 and I'm having a packaging
> problem...
> I have 2 modules, 'api' and 'model' using JDK 1.5 and retrotranslator
> activated.
> These seem to be fine, the JDK 1.4 artifacts are being created and
> installed in the local repository (using 'Locally install artifact').
> Another module, 'portal' depends on these 2 modules and specifies the 'j4'
> classifier for them.
> AFAIS, when running 'Package artifact' from Eclipse, the JDK 1.5 modules
> are being used and the 'j4' classifier is being added to them(which
> confused me and made me think at first the retrotranslator wasn't working).
> When using Maven from the command line, the proper jars are used.
> I suppose the problem comes from the fact that Q4E detects that the
> projects of the first 2 modules are present in the workspace and uses
> them...
> Is there anything I can do?
|
|
|
|
Powered by
FUDForum. Page generated in 0.03527 seconds
] 
Search
Help
Register
Login
Home
