[JBoss JIRA] (JBDS-3573) JBDS 91.0.beta1 is "chatty" when the UI is opened
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-3573:
----------------------------------
Summary: JBDS 91.0.beta1 is "chatty" when the UI is opened
Key: JBDS-3573
URL: https://issues.jboss.org/browse/JBDS-3573
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: welcome
Affects Versions: 9.1.0.Beta1
Environment: Version: 9.1.0.Beta1
Build id: Beta1-v20151210-1215-B180
Build date: 20151210-1215
Reporter: Len DiMaggio
Priority: Minor
The following is written to stdout when the UI is opened:
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://1068.fwk1984954272:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://1068.fwk1984954272:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
14:52:13.313 [Worker-6] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml]
14:52:14.543 [Worker-16] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/ldimaggi/.m2/repository
14:52:14.552 [Worker-16] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/ldimaggi/.m2/repository
14:52:14.553 [Worker-16] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml]
14:52:14.556 [Worker-16] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3565) Add missing JBDS TP bits to JBDS IS update site zip
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3565?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3565:
-----------------------------
Summary: Add missing JBDS TP bits to JBDS IS update site zip (was: Include Target Platform Zip with JBDS for offline install on CSP)
> Add missing JBDS TP bits to JBDS IS update site zip
> ---------------------------------------------------
>
> Key: JBDS-3565
> URL: https://issues.jboss.org/browse/JBDS-3565
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.1.0.Beta1
> Environment: Customer Support Portal
> Reporter: Mustafa Musaji
> Assignee: Nick Boldt
> Fix For: 9.1.0.Beta2
>
>
> Offline ZIP installation allows for JBDSIS tooling to be installed when there is no internet connection available. These zips for the JBDSIS and early access tooling is available from the CSP, however, some dependencies for this tooling is only available on the Target Platform zip.
> This TP zip is only available on the jboss.org site https://devstudio.jboss.com/9.0/stable/updates/ and not on the customer portal.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21278) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Webservices]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21278?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-21278.
------------------------------
Resolution: Rejected
> For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Webservices]
> ---------------------------------------------------------
>
> Key: JBIDE-21278
> URL: https://issues.jboss.org/browse/JBIDE-21278
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Webservices]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), you do *not* need to do so again.
> Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT).
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta1x
> git push origin jbosstools-4.3.1.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and
> * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21267) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21267?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21267:
------------------------------------
What about these 5 commits in 4.3.x since we released 4.3.0.Final?
https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.3.x
> For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21267
> URL: https://issues.jboss.org/browse/JBIDE-21267
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), you do *not* need to do so again.
> Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT).
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta1x
> git push origin jbosstools-4.3.1.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and
> * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21215) IUs missing from snapshot update site while site is being published / outdated metadata needs to be refreshed within Eclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21215?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21215:
------------------------------------
An open jira is not the same as a data set. You guys randomly complaining is not the same as collecting useful data.
Once again, you're saying two contradictory things: "I do this pretty rare and it hits me often enough" If it's rare, it's not often. If it's often, it's not rare. :)
If this is an upstream issue w/ stale p2 metadata, please report it upstream and link that one to this issue. Thanks!
> IUs missing from snapshot update site while site is being published / outdated metadata needs to be refreshed within Eclipse
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21215
> URL: https://issues.jboss.org/browse/JBIDE-21215
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1
>
>
> running updates from: http://download.jboss.org/jbosstools/mars/snapshots/updates/
> I get this error:
> {quote}
> An error occurred while collecting items to be installed
> session context was:(profile=_Users_max_products_eclipse_jee-mars3_Eclipse.app_Contents_Eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
> No repository found containing: osgi.bundle,org.jboss.tools.common,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.core,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.el.core,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.jdt.debug,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.jdt.debug.ui,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.resref.core,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.text.xml,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.ui,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.validation,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.foundation.checkup,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.foundation.core,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.foundation.ui,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.cdk.server,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.client,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.common.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.common.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.egit.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.egit.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.client,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.runtime.core,3.1.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.runtime.ui,3.1.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.stacks.core,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.usage,2.1.1.Beta1-v20151204-0542-B55
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.cdk.feature,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.express.feature,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.feature,3.1.0.Beta1-v20151205-0342-B106
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21284) compare baselines failing in 4.3.x branch for aggregate site builds (central and EA)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21284?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-21284.
------------------------------
Builds are back to blue. Also pushed the cherry-picked commit to 4.3.1.Beta1x branch.
https://github.com/jbosstools/jbosstools-build-sites/commits/jbosstools-4...
> compare baselines failing in 4.3.x branch for aggregate site builds (central and EA)
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21284
> URL: https://issues.jboss.org/browse/JBIDE-21284
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, upstream
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.3.1.Beta1, 4.3.1.Beta2
>
>
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.24.0:compare-version-with-baselines (default) on project org.jboss.tools.site.central: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4": For input string: "raw:4" -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.24.0:compare-version-with-baselines (default) on project org.jboss.tools.site.central: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4"
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> 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:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoFailureException: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4"
> at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:176)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: java.lang.IllegalArgumentException: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4"
> at org.osgi.framework.Version.parseInt(Version.java:170)
> at org.osgi.framework.Version.<init>(Version.java:126)
> at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:120)
> ... 21 more
> Caused by: java.lang.NumberFormatException: For input string: "raw:4"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.osgi.framework.Version.parseInt(Version.java:168)
> ... 23 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months