Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » IAM (Eclipse Integration for Apache Maven) » packaging problem
packaging problem [message #15801] Thu, 13 November 2008 07:49 Go to next message
Andrei Ivanov is currently offline Andrei Ivanov
Messages: 4
Registered: July 2009
Junior Member
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 #15823 is a reply to message #15801] Thu, 13 November 2008 11:22 Go to previous messageGo to next message
Abel Mui is currently offline 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 #15860 is a reply to message #15823] Thu, 13 November 2008 11:35 Go to previous message
Andrei Ivanov is currently offline Andrei Ivanov
Messages: 4
Registered: July 2009
Junior Member
Abel Muiño wrote:
> 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.
Well.. closing the projects wouldn't be very good for me because they
are also actively developed.

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

I'll create a ticket then... with a sample hopefully.
Thank you.
Re: packaging problem [message #567960 is a reply to message #15801] Thu, 13 November 2008 11:22 Go to previous message
Abel Mui is currently offline 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 #568011 is a reply to message #15823] Thu, 13 November 2008 11:35 Go to previous message
Andrei Ivanov is currently offline Andrei Ivanov
Messages: 4
Registered: July 2009
Junior Member
Abel Muiño wrote:
> 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.
Well.. closing the projects wouldn't be very good for me because they
are also actively developed.

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

I'll create a ticket then... with a sample hopefully.
Thank you.
Previous Topic:IAM installation results in extremely slow Eclipse startup
Next Topic:Maven Core artifacts
Goto Forum:
  


Current Time: Fri Aug 22 21:48:20 EDT 2014

Powered by FUDForum. Page generated in 0.02414 seconds