Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Run task before the target is resolved (target-resolve phase..)?

You are solving wrong problem, I think. The only reason you want to
create target platform before dependency resolution is to workaround PDE
limitations. ;-)

Maven defers dependency resolution until it is actually necessary at the
cost of less precise ordering of reactor modules (it is theoretically
possible to have wrong reactor order when there is indirect dependency
between modules and remote artifacts). We can implement similar approach
in Tycho, i.e. calculate module order based on project metadata only and
resolve project target platform and dependencies at a later stage. Not
sure if this is worth the hassle, however.

--
Regards,
Igor

On 11-07-26 1:47 PM, Oberlies, Tobias wrote:
Dependency resolution needs to happen before the module build starts, because it determines the module build order.

My idea to solve this issue was to introduce a lifecycle phase before module ordering (and just execute that phase in an arbitrary order), but I couldn't convince the Maven guys to implement this for me, so this will probably not come - unless you or someone else is willing to implement this in Maven...

Regards
Tobias


-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-
bounces@xxxxxxxxxxx] On Behalf Of Niels Nielsen
Sent: 25 July 2011 17:49
To: Tycho user list
Subject: Re: [tycho-user] Run task before the target is resolved (target-
resolve phase..)?

Hi,

I have been using Tycho on and off for the last year without ever going
into details.
However, it has always been strange to me this fact that dependency
resolution has to happen before the build cycle starts.
I assume this is eclipse resolver specifics, but it does have some
drawbacks

1) It is error prone to any propertybased specification of resolver
definition in parent poms as the parent pom is not build before
subprojects are analyzed
2) It prevents generating a target platform without having to have a
bootstrap mechanism.
3) Problems wrt dependency resolution is highlighted outside of the
individual project containing the error, which is confusing and difficult
to trace.

Now, given that it is so contrary to normal maven dependency resolutions,
how come it is not possible to work around it or at least lazy load the
dependency mechanism?

Regards
/Niels

-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-
bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
Sent: 16 July 2011 07:24
To: tycho-user@xxxxxxxxxxx
Subject: Re: [tycho-user] Run task before the target is resolved (target-
resolve phase..)?

Dependency resolution has to happen before build lifecycle starts, so it
is not possible to run any maven goals before it.

--
Regards,
Igor

On 11-07-15 5:22 PM, motes motes wrote:
In a maven3/tycho project I would like to run an ant task before the
target is resolved. But it seems that the target is resolved before
any of the standard maven phases is run. Is there someway to do stuff
before the target is resolved, I have tried:

						<phase>generate-resources</phase>
						<goals>
							<goal>copy</goal>
						</goals>

but still the target is resolved (and the projec fails if the resolve
fails) before this task is executed.
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user


Back to the top