Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Maven/Tycho dependencies not available in IDE/PDE

Hi Mikhail -

Right .. I really prefer to leave the execution environment unspecified.  For these project, the weakest precondition always seems to be any environment.

<rant>
I really wish the tooling would respect that the environment is undefined.  Just leave things alone that don't need to be changed.  Especially the project's language version and the JRE on the classpath.  Regardless of how they are set (unset), just leave it alone.
</rant>

I suspect you are correct that the unspecified execution environment is the source of these annoying issues.  I guess I'll just have to work around it.

Thanks
- Lee

On Wed, Oct 28, 2015 at 12:32 AM, Mikhail Kalkov <mikhail.kalkov@xxxxxxxxx> wrote:

Hi Lee,

The bit about "projects that DO NOT have a POM" was crucial. This sounds like when a pom.xml is created from scratch by the "Convert to Maven project" command, your Eclipse project settings are not copied to pom file. Did you have a Bundle-RequiredExecutionEnvironment configured in your project before conversion?

Den 26 okt 2015 18:23 skrev "Lee Carver" <leeca@xxxxxxxxxxx>:
Max -

That's a swing and a miss ...

As I noted originally, its the "Configure > Convert to Maven Project" (from m2e?) that is yanking around the development environment.  I use this for the projects the DO NOT have a POM.  It's the only "conforming" process that I know that can change a Eclipse project nature.

Thanks
- Lee

On Mon, Oct 26, 2015 at 7:28 AM, Max Rydahl Andersen <manderse@xxxxxxxxxx> wrote:

Due to the heavy-handed changes made by the Configure > Convert to Maven
Project process, I had removed some of the created configuration files.
Most obnoxious was Maven's insistence to reset the project to Java 1.5
(please, just leave it alone!).

If you don't want it to Java 1.5 then make sure your pom.xml actually
say so by specifying the exact java version you target. Maven defaults to Java 5,
so m2e is just letting you know!

See: http://stackoverflow.com/questions/3539139/what-causes-a-new-maven-project-in-eclipse-to-use-java-1-5-instead-of-java-1-6-b

/max

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user


_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user


Back to the top