Re: Failures building Eclipse 4.13 with maven-3.6.2
Hi, I didn't find a matching issue, so I raised MNG-6765 so that it can be tracked. https://issues.apache.org/jira/browse/MNG-6765 Cheers. -- Jonathan Chen On Sat, 14 Sep 2019 at 19:47, Jonathan Chen wrote: > > Hi, > > Thanks for that. Is there a JIRA reference for this bug? > > Cheers. > -- > Jonathan Chen > > On Sat, 14 Sep 2019 at 17:39, Jeff MAURY wrote: > > > > This is a know case between tycho pomless and maven 3.6.2 > > > > Le sam. 14 sept. 2019 à 05:26, Jonathan Chen a écrit : > > > > > Hi, > > > > > > I'm currently attempting to build Eclipse 4.13 from source using > > > maven-3.6.2, and I'm seeing these current failures: > > > [INFO] Scanning for projects... > > > [ERROR] [ERROR] Some problems were encountered while processing the POMs: > > > [FATAL] Non-readable POM > > > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.cdcfoundation10/.polyglot.build.properties: > > > input contained no data @ > > > [FATAL] Non-readable POM > > > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.cdcfoundation11/.polyglot.build.properties: > > > input contained no data @ > > > [FATAL] Non-readable POM > > > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.feature/.polyglot.build.properties: > > > input contained no data @ > > > [FATAL] Non-readable POM > > > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se12/.polyglot.build.properties: > > > input contained no data @ > > > [FATAL] Non-readable POM > > > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se13/.polyglot.build.properties: > > > input contained no data @ > > > [FATAL] Non-readable POM > > > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se14/.polyglot.build.properties: > > > input contained no data @ > > > [FATAL] Non-readable POM > > > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se15/.polyglot.build.properties: > > > input contained no data @ > > > [FATAL] Non-readable POM > > > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase16/.polyglot.build.properties: > > > input contained no data @ > > > [FATAL] Non-readable POM > > > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase17/.polyglot.build.properties: > > > input contained no data @ > > > ... > > > > > > It appears that the pom-less builds are failing due to a missing > > > .polyglot.build.properties. These are transient files that are removed > > > once the compiling JVM exits. Something in the 3.6.2 lifecycle has > > > changed such that the files are not staying long enough to be > > > available for dependency-resolution. > > > > > > If I downgrade to maven-3.6.1 or maven-3.6.0, these errors do not arise. > > > > > > Cheers. > > > -- > > > Jonathan Chen > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Failures building Eclipse 4.13 with maven-3.6.2
Hi, Thanks for that. Is there a JIRA reference for this bug? Cheers. -- Jonathan Chen On Sat, 14 Sep 2019 at 17:39, Jeff MAURY wrote: > > This is a know case between tycho pomless and maven 3.6.2 > > Le sam. 14 sept. 2019 à 05:26, Jonathan Chen a écrit : > > > Hi, > > > > I'm currently attempting to build Eclipse 4.13 from source using > > maven-3.6.2, and I'm seeing these current failures: > > [INFO] Scanning for projects... > > [ERROR] [ERROR] Some problems were encountered while processing the POMs: > > [FATAL] Non-readable POM > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.cdcfoundation10/.polyglot.build.properties: > > input contained no data @ > > [FATAL] Non-readable POM > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.cdcfoundation11/.polyglot.build.properties: > > input contained no data @ > > [FATAL] Non-readable POM > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.feature/.polyglot.build.properties: > > input contained no data @ > > [FATAL] Non-readable POM > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se12/.polyglot.build.properties: > > input contained no data @ > > [FATAL] Non-readable POM > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se13/.polyglot.build.properties: > > input contained no data @ > > [FATAL] Non-readable POM > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se14/.polyglot.build.properties: > > input contained no data @ > > [FATAL] Non-readable POM > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se15/.polyglot.build.properties: > > input contained no data @ > > [FATAL] Non-readable POM > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase16/.polyglot.build.properties: > > input contained no data @ > > [FATAL] Non-readable POM > > > > /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase17/.polyglot.build.properties: > > input contained no data @ > > ... > > > > It appears that the pom-less builds are failing due to a missing > > .polyglot.build.properties. These are transient files that are removed > > once the compiling JVM exits. Something in the 3.6.2 lifecycle has > > changed such that the files are not staying long enough to be > > available for dependency-resolution. > > > > If I downgrade to maven-3.6.1 or maven-3.6.0, these errors do not arise. > > > > Cheers. > > -- > > Jonathan Chen > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Failures building Eclipse 4.13 with maven-3.6.2
Hi, I'm currently attempting to build Eclipse 4.13 from source using maven-3.6.2, and I'm seeing these current failures: [INFO] Scanning for projects... [ERROR] [ERROR] Some problems were encountered while processing the POMs: [FATAL] Non-readable POM /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.cdcfoundation10/.polyglot.build.properties: input contained no data @ [FATAL] Non-readable POM /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.cdcfoundation11/.polyglot.build.properties: input contained no data @ [FATAL] Non-readable POM /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.feature/.polyglot.build.properties: input contained no data @ [FATAL] Non-readable POM /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se12/.polyglot.build.properties: input contained no data @ [FATAL] Non-readable POM /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se13/.polyglot.build.properties: input contained no data @ [FATAL] Non-readable POM /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se14/.polyglot.build.properties: input contained no data @ [FATAL] Non-readable POM /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se15/.polyglot.build.properties: input contained no data @ [FATAL] Non-readable POM /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase16/.polyglot.build.properties: input contained no data @ [FATAL] Non-readable POM /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase17/.polyglot.build.properties: input contained no data @ ... It appears that the pom-less builds are failing due to a missing .polyglot.build.properties. These are transient files that are removed once the compiling JVM exits. Something in the 3.6.2 lifecycle has changed such that the files are not staying long enough to be available for dependency-resolution. If I downgrade to maven-3.6.1 or maven-3.6.0, these errors do not arise. Cheers. -- Jonathan Chen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
m2 ear plugin and resource filters.
Hi all,
I'm running Maven 2.0.7 and I'm trying to get resource filtering
working with m2's ear plugin. I have a file which I'm trying to get
certain properties replaced on a mvn package.
src/main/application/META-INF/geronimo.xml:
?xml version=1.0 encoding=UTF-8?
application
xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-1.2;
xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2;
environment
xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2;
moduleId
groupId${pom.groupId}/groupId
artifactId${pom.artifactId}/artifactId
version${pom.version}/version
typeear/type
/moduleId
/environment
/application
Ideally, the ${pom.*} properties are replaced with the values from
pom.xml; but for some reason, I can't seem to get it working with:
pom.xml:
?xml version=1.0 encoding=UTF-8?
project
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
nameEAR goal test/name
groupIdtest/groupId
artifactIdear-goal/artifactId
version1.0-SNAPSHOT/version
packagingear/packaging
build
resources
resource
filteringtrue/filtering
directorysrc/main/application/META-INF/directory
includes
include*.xml/include
/includes
/resource
/resources
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
configuration
version5/version
/configuration
/plugin
/plugins
/build
/project
Can anyone on the list see what I'm doing wrong? Any help appreciated.
Cheers.
--
Jonathan Chen [EMAIL PROTECTED]
--
Don't worry about avoiding temptation,
as you grow older, it starts avoiding you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: m2 ear plugin and resource filters.
On Tue, Aug 28, 2007 at 05:32:25PM +0200, Stephane Nicoll wrote: You're hacking the ear's plugin own resource directory with a standard resource. This own resource dir was a design error in the early days. Anyway, you might be able to configure a custom execution of the resource plugin with filtering enabled. But move your files out of src/main/application first. There's an issue in Jira to automatically support filtering for this directory. I guess I'll do that. Thanks for that. The vote is in. -- Jonathan Chen [EMAIL PROTECTED] -- The reason why worry kills more people than work is that more people worry than work. - Robert Frost - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
