[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2635:
--------------------------------------
Fix Version/s: 7.1.0.Alpha2
(was: 7.1.0.Alpha1)
> Installation sometimes fail with bundle was not found on Windows
> ----------------------------------------------------------------
>
> Key: JBDS-2635
> URL: https://issues.jboss.org/browse/JBDS-2635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.0.0.Beta1
> Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: 7.1.0.Alpha2
>
> Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log
>
>
> For the first time JBDS 7.0.0.Beta1 failed on windows8:
> {code}
> An error occurred while installing the items
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
> The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found.
> Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-5506) Cannot publish ESB to server
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-5506?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky closed JBIDE-5506.
------------------------------------
Outdated
> Cannot publish ESB to server
> ----------------------------
>
> Key: JBIDE-5506
> URL: https://issues.jboss.org/browse/JBIDE-5506
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb, server
> Affects Versions: 3.1.0.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Denny Xu
> Priority: Blocker
> Fix For: 3.1.0.CR1
>
>
> I cannot publish nor export any ESB archives.
> I get several errors:
> Dragging an .esb file to a Deploy only server or AS 5 gives me:
> Invalid matching rules used: 4.7/4
> At deploy:
> java.lang.NullPointerException
> at org.jboss.ide.eclipse.as.core.server.internal.DeployableServer.getRuntime(DeployableServer.java:169)
> at org.jboss.ide.eclipse.as.core.server.internal.DeployableServer.getDeployFolder(DeployableServer.java:117)
> at org.jboss.ide.eclipse.as.core.publishers.PublishUtil.getDeployPath(PublishUtil.java:102)
> at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.fullPublish(JstPublisher.java:104)
> at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publishModule(JstPublisher.java:93)
> at org.jboss.ide.eclipse.as.core.publishers.LocalPublishMethod.publishModule(LocalPublishMethod.java:71)
> at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:65)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:948)
> at org.eclipse.wst.server.core.model.ServerBe
> And export I simply couldn't get to work!
> Which combination is supposed to work !?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBDS-2389) cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2389?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-2389.
---------------------------------------
Resolution: Won't Fix
Resolving issue - don't see how this can be solved cleanly and since it is not a supported usecase its time to remove it from jira.
if comes up again with a supported usecase/issue we can reopeon.
> cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2389
> URL: https://issues.jboss.org/browse/JBDS-2389
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, updatesite
> Affects Versions: 6.0.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.Alpha1, 7.1.x
>
>
> Steps to repro:
> Unpack bare Juno JEE.
> Install JBDS BYOE feature ("Core Features"). Restart
> Install JBDS Branded Product Feature. Restart.
> Uninstall JBDS Branded Product Feature (or revert configuration to previous). Restart. Eclipse is now broken:
> {code}
> java.lang.RuntimeException: Application "" could not be found in the registry.
> {code}
> Addtional info:
> {quote}
> Bare Juno JEE eclipse.ini:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -product
> org.eclipse.epp.package.jee.product
> --launcher.defaultAction
> openFile
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Dosgi.requiredJavaVersion=1.5
> -Dhelp.lucene.tokenizer=standard
> -XX:MaxPermSize=256m
> -Xms40m
> -Xmx512m
> {code}
> or, for Eclipse Platform Binary:
> {code}
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms40m
> -Xmx384m
> {code}
> After installing JBDS BYOE:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms512m
> -Xmx1024m
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> {code}
> After installing JBDS branded product, eclipse.ini becomes jbdevstudio.ini:
> {code}
> $➔ cat eclipse/jbdevstudio.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> -Xms512m
> -Xmx1024m
> -Dosgi.instance.area.default=(a)user.home/workspace
> {code}
> After UNINSTALLING JBDS branded product (to drop back to Eclipse + JBDS BYOE), can no longer start Eclipse. Here is the resulting eclipse.ini file:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> -Xms512m
> -Xmx1024m
> {code}
> {quote}
> So, I think we need an instructions.unconfigure in com.jboss.jbds.p2.inf to remove these lines
> {code}
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> {code}
> and replace them with the following when JBDS is uninstalled:
> {code}
> -application
> org.eclipse.ui.ide.workbench
> -showsplash
> org.eclipse.platform
> {code}
> Also need to know what happens if there are two -product directives... can we just
> add (and later remove, when uninstalling) our product to the list, or must we replace
> any existing -product entries with ours?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15462) bump openshift plugins to 2.6.0
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-15462:
----------------------------------------
Summary: bump openshift plugins to 2.6.0
Key: JBIDE-15462
URL: https://issues.jboss.org/browse/JBIDE-15462
Project: Tools (JBoss Tools)
Issue Type: Task
Components: openshift
Affects Versions: 4.2.0.Alpha1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.2.0.Alpha1
We have to bump the plugins from 2.5.0 -> 2.6.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-5482) Cannot export ESB 4.7 (SOA-P 5) project
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-5482?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky closed JBIDE-5482.
------------------------------------
Len verified that a long time ago
> Cannot export ESB 4.7 (SOA-P 5) project
> ---------------------------------------
>
> Key: JBIDE-5482
> URL: https://issues.jboss.org/browse/JBIDE-5482
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 3.1.0.M4
> Environment: JBoss Developer Studio 3.0.0.RC1 (v200912042231M-H29)
> Reporter: Len DiMaggio
> Assignee: Brian Fitzpatrick
> Priority: Blocker
> Fix For: 3.1.0.CR2
>
> Attachments: log, simpleESB.tar
>
>
> Steps to recreate:
> 1) Create new JBossESB project in JBDS - use samples/quickstarts/helloworld
> 2) Attempt to export to .esb file
> Attached log file shows the error raised - attached .tar file contains the project.
> !ENTRY org.eclipse.wst.common.frameworks 4 0 2009-12-15 15:13:54.386
> !MESSAGE Error exportinghello
> !STACK 0
> org.eclipse.core.commands.ExecutionException: Error exportinghello
> at org.jboss.ide.eclipse.as.wtp.core.vcf.ModuleExportOperation.execute(ModuleExportOperation.java:117)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:376)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:401)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:352)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:242)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:214)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:202)
> at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelWizard$1$CatchThrowableRunnableWithProgress.run(DataModelWizard.java:218)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Caused by: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.SaveFailureException
> at org.jboss.ide.eclipse.as.wtp.core.vcf.ModuleExportOperation.export(ModuleExportOperation.java:269)
> at org.jboss.ide.eclipse.as.wtp.core.vcf.ModuleExportOperation.execute(ModuleExportOperation.java:114)
> ... 10 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15460) bumping plugin version with tycho 0.18.1 fails with NPE
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-15460:
----------------------------------------
Summary: bumping plugin version with tycho 0.18.1 fails with NPE
Key: JBIDE-15460
URL: https://issues.jboss.org/browse/JBIDE-15460
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.Alpha1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.2.0.Alpha1
0) bumped plugin version:
{code}
mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=2.5.1-SNAPSHOT
{code}
which ended up in tycho failing with an NPE:
{code}
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version (default-cli) on project openshift: Execution default-cli of goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version failed. NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version (default-cli) on project openshift: Execution default-cli of goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version failed.
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: java.lang.NullPointerException
at org.eclipse.tycho.versions.pom.GAV.getGroupId(GAV.java:23)
at org.eclipse.tycho.versions.manipulation.PomManipulator.isGavEquals(PomManipulator.java:154)
at org.eclipse.tycho.versions.manipulation.PomManipulator.changePlugins(PomManipulator.java:129)
at org.eclipse.tycho.versions.manipulation.PomManipulator.changeBuild(PomManipulator.java:117)
at org.eclipse.tycho.versions.manipulation.PomManipulator.applyChange(PomManipulator.java:83)
at org.eclipse.tycho.versions.engine.VersionsEngine.applyChange(VersionsEngine.java:165)
at org.eclipse.tycho.versions.engine.VersionsEngine.apply(VersionsEngine.java:142)
at org.eclipse.tycho.versions.SetMojo.execute(SetMojo.java:78)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
{code}
there are 2 ways to fix this:
* use tycho 0.17 (not 0.18.1):
{code}
mvn org.eclipse.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=2.5.1-SNAPSHOT
{code}
* look for artifactId that's missing a groupId. For me it was using maven-clean-plugin:
{code}
<build>
<plugins>
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.7</version><!--$NO-MVN-MAN-VER$-->
<executions>
<execution>
<id>get-libs</id>
<goals>
<goal>copy</goal>
</goals>
<phase>generate-resources</phase>
</execution>
</executions>
{code}
correcting it fixed the NPE in tycho 0.18.1
{code}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.7</version><!--$NO-MVN-MAN-VER$-->
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15460) bumping plugin version with tycho 0.18.1 fails with NPE
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15460?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15460:
------------------------------------------
there are 2 ways to fix this:
* use tycho 0.17 (not 0.18.1):
{code}
mvn org.eclipse.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=2.5.1-SNAPSHOT
{code}
* look for artifactId that's missing a groupId. For me it was using maven-clean-plugin:
{code}
<build>
<plugins>
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.7</version><!--$NO-MVN-MAN-VER$-->
<executions>
<execution>
<id>get-libs</id>
<goals>
<goal>copy</goal>
</goals>
<phase>generate-resources</phase>
</execution>
</executions>
{code}
correcting it fixed the NPE in tycho 0.18.1
{code}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.7</version><!--$NO-MVN-MAN-VER$-->
{code}
> bumping plugin version with tycho 0.18.1 fails with NPE
> -------------------------------------------------------
>
> Key: JBIDE-15460
> URL: https://issues.jboss.org/browse/JBIDE-15460
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
>
> Try to bump the version of the plugins:
> {code}
> mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=2.5.1-SNAPSHOT
> {code}
> it ends in tycho failing with an NPE:
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version (default-cli) on project openshift: Execution default-cli of goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version failed. NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version (default-cli) on project openshift: Execution default-cli of goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.lang.NullPointerException
> at org.eclipse.tycho.versions.pom.GAV.getGroupId(GAV.java:23)
> at org.eclipse.tycho.versions.manipulation.PomManipulator.isGavEquals(PomManipulator.java:154)
> at org.eclipse.tycho.versions.manipulation.PomManipulator.changePlugins(PomManipulator.java:129)
> at org.eclipse.tycho.versions.manipulation.PomManipulator.changeBuild(PomManipulator.java:117)
> at org.eclipse.tycho.versions.manipulation.PomManipulator.applyChange(PomManipulator.java:83)
> at org.eclipse.tycho.versions.engine.VersionsEngine.applyChange(VersionsEngine.java:165)
> at org.eclipse.tycho.versions.engine.VersionsEngine.apply(VersionsEngine.java:142)
> at org.eclipse.tycho.versions.SetMojo.execute(SetMojo.java:78)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> ... 20 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months