Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Reconsider allowing tycho-eclipserun-plugin in an aggregator POM

I had previously read this after running into the same thing myself.

http://dev.eclipse.org/mhonarc/lists/tycho-user/msg02972.html

The thread is about 0.15.0 and we never took up 0.16 because of the bug with encrypted passwords, so it's possible that it changed in 0.16 thus potentially rendering this thread moot. 

-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Sievers, Jan
Sent: Tuesday, March 19, 2013 12:06 PM
To: Tycho user list
Subject: Re: [tycho-user] Reconsider allowing tycho-eclipserun-plugin in an aggregator POM

>What's the point of requiring that the eclipserun plugin only execute 
>in a project that has a Tycho packaging type if we can't have access to the feature/plugin that we're building?

I can't see any restriction on packaging types in [1]

Jan

[1] http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/tree/tycho-eclipserun-plugin/src/main/java/org/eclipse/tycho/extras/eclipserun/EclipseRunMojo.java
 
-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Sievers, Jan
Sent: Tuesday, March 19, 2013 11:14 AM
To: Tycho user list
Subject: Re: [tycho-user] Reconsider allowing tycho-eclipserun-plugin in an aggregator POM

not sure I understand your usecase.

Regarding using what is being built in the same reactor:
this can't be made to work reliably from a module dependency order point of view which is why we deliberately removed this option.

This is for the same reason as e.g. you can't use a maven plugin in the same reactor where you build it.

Jan

From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Justin Georgeson
Sent: Dienstag, 19. März 2013 17:05
To: Tycho user list
Subject: [tycho-user] Reconsider allowing tycho-eclipserun-plugin in an aggregator POM

This isn't about testing the staged 0.17.0 so I didn't want to hijack that thread.
 
Since 0.17.0 changes the eclipserun plugin so that it can't easily be used referencing features/plugins we're building in the same reactor, would it be possible to reconsider (for 0.18.0) being able to use the eclipserun plugin in an aggregator POM to do once-per-reactor tasks at the beginning of a build?
 
 
________________________________________
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
_______________________________________________
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