[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [m2e-users] Eclipse Mars + Takari team - fail to install
|
@Fred thank you for checking Java EE mavenarchiver issue. I've updated Takari Team feature to include mavenarchiver 0.17, so hopefully this will work for Mars now.
@Dan Takari Team feature provides one known to work together set of component versions, which we use with Eclipse SDK and as part of custom Eclipse distro. Other combinations of the reasonably recent versions of the same set of components will likely work, but you will need to find what works with your Eclipse distro yourself.
On Sun, Aug 23, 2015, at 06:34 PM, Dan Tran wrote:
Few more facts:
* Eclipse Luna SR2 also has mavenarchiver (0.16), but the takari-team has no problem install
* Eclipse STS 3.6.4 ( Luna SRC2 base) also see the similar issue, but direct installation using UI able to continue with some warnings
* Have not tried with STS 3.7 (Mars base)
So perhaps, the root cause is from Eclipse?
Thanks
-Dan
I just built mavenarchiver 0.17.0 locally, so with a today's timestamp, and successfully installed it on the Java EE distro. So, other than the 0.17.0 lower constraint in Java EE, there really is no specific version locking there.
Yes. Takari feature requires
specific versions of everything. But mavenarchiver configurator version
must be locked elsewhere too, otherwise installation would have succeeded.
--
Regards,
Igor
On
August 23, 2015 3:34:34 PM Fred Bricon <fbricon@xxxxxxxxx> wrote:
Igor m2e-wtp requires mavenarchiver 0.17.0+, but doesn't
lock to any specific version.
actually JEE comes with the 0.17, so perhaps upgrade takari-team
to use 0.17 may work?
Thanks
Ouch!!! It is a hard requirement from Takari since we need
JEE
JEE comes with maven-archive connector version 0.16.0.201410091840 and Takari team
comes with 0.17
Is there a way to remove 0.16 from JEE
prior to takari-team installation?
Thanks
-Dan
Looks like something in Eclipse for Java EE has hard dependency
on specific version of mavenarchiver, which conflicts with mavenarchiver
version required by Takari Team feature. Nothing we can do from our side to
fix this. If you don't specifically need Java EE functionality, I
suggest you use clean(er) Eclipse distribution, "for Java" or
"SDK". Or just pick the same components that are included in
Takari Team feature
On Sun, Aug 23, 2015, at 12:00 AM, Dan Tran wrote:
HI
I have a put together a set of Maven poms to auto provision Eclipse
and additional features such as takari-team required by my dev team
The pom uses exec-maven-plugin to with following similar config
<execution>
<id>install-m2extra-takari-team</id>
<phase>process-sources</phase>
<goals>
<goal>exec</goal>
</goals>
<configuration>
<executable>${eclipse.home}/${eclipse.cmd}</executable>
<arguments>
<argument>-clean</argument>
<argument>-purgeHistory</argument>
<argument>-application</argument>
<argument>org.eclipse.equinox.p2.director</argument>
<argument>-noSplash</argument>
<argument>-repository</argument>
<!-- this assumes takari actively maintains the
latest -->
<argument>-installIUs</argument>
<argument>io.takari.m2e.team.feature.feature.group</argument>
</arguments>
</configuration>
</execution>
This works for Eclipse Luna SR2 but not with Eclipse Mars
here is the error from command line
[INFO] --- exec-maven-plugin:1.4.0:exec
(install-m2extra-takari-team) @ eclipse-jee ---
org.eclipse.m2e.logback.configuration: The
org.eclipse.m2e.logback.configuration bundle was activated before the state
l
ocation was initialized. Will retry after the state location is
initialized.
Installing io.takari.m2e.team.feature.feature.group
0.1.0.201508220400.
Installation failed.
Cannot complete the install because of a conflicting dependency.
Software being installed: Takari TEAM for Eclipse 0.1.0.201508220400
(io.takari.m2e.team.feature.feature.group 0.1.0.20
1508220400)
Software currently installed: Eclipse IDE for Java EE Developers
4.5.0.20150621-1200 (epp.package.jee 4.5.0.20150621-12
00)
Only one of the following can be installed at once:
m2e connector for the mavenarchiver and pom properties
0.17.0.201502101659-signed-20150525172209 (org.sonatype.m2e.mav
enarchiver 0.17.0.201502101659-signed-20150525172209)
m2e connector for the mavenarchiver and pom properties
0.16.0.201410091840 (org.sonatype.m2e.mavenarchiver 0.16.0.2014
10091840)
is it something that Takaki can fix?
Thanks
-Dan
PS. I am using Java 8
_______________________________________________
m2e-users mailing list
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
_______________________________________________
m2e-users mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
_______________________________________________
m2e-users mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
--
"Have you tried turning it off and on again" - The
IT Crowd
_______________________________________________
m2e-users mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
--
"Have you tried turning it off and on again" - The IT Crowd
_______________________________________________
m2e-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
_______________________________________________
m2e-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit