eclipse : [WARNING] build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing
I've installed m2 Sonatype plugin in eclipse. When I execute package, the following warning messages appear: [WARNING] Some problems were encountered while building the effective model for stockdomain:stockdomain:war:1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 11, column 12 [WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:exec-maven-plugin is missing. @ line 26, column 12 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. Many thanks fo advise on how to get rid of these warning. fv1961 -- View this message in context: http://maven.40175.n5.nabble.com/eclipse-WARNING-build-plugins-plugin-version-for-org-apache-maven-plugins-maven-compiler-plugin-is-mg-tp3318900p3318900.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Request received: eclipse : [WARNING] build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler... (ticket #21939)
## In replies all text above this line is added to the ticket ## Request received: eclipse : [WARNING] build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler... (ticket #21939) Your request (#21939) has been received, and is being reviewed by our support staff. To review the status of the request and add additional comments, follow the link below: http://support.boxee.tv/tickets/21939 -- Maven Users List, Dec-27 04:07 am (EST): I've installed m2 Sonatype plugin in eclipse. When I execute package, the following warning messages appear: [WARNING] Some problems were encountered while building the effective model for stockdomain:stockdomain:war:1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 11, column 12 [WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:exec-maven-plugin is missing. @ line 26, column 12 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. Many thanks fo advise on how to get rid of these warning. fv1961 -- View this message in context: http://maven.40175.n5.nabble.com/eclipse-WARNING-build-plugins-plugin-version-for-org-apache-maven-plugins-maven-compiler-plugin-is-mg-tp3318900p3318900.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This email is a service from Boxee Support
maven 3.0.1 pulling in transient dependencies of a provided dependency as compile-scoped
i have a maven project that contains the following dependency: dependency groupIdorg.jboss.ejb3/groupId artifactIdjboss-ejb3-core/artifactId version1.6.3/version scopeprovided/scope /dependency this is part of a module that produces an ear artifact. according to the maven dependency scope doc ( http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html) the transient dependencies of a provided-scoped dependency are either scoped as provided or not treated at all. and yet in my case im seeing this as part of the build (produced with -X): [DEBUG] com.emc.illuminator:illuminator-ear:ear:6.0-SNAPSHOT [DEBUG]...some direct dependencies edited out for brevity's sake... [DEBUG]org.jboss.ejb3:jboss-ejb3-core:jar:1.6.3:provided [DEBUG] javassist:javassist:jar:3.7.1.GA:compile [DEBUG] org.hibernate:hibernate-core:jar:3.3.1.GA:provided [DEBUG] antlr:antlr:jar:2.7.6:provided [DEBUG] dom4j:dom4j:jar:1.6.1:compile notice that javassist and dom4j are upgraded to compile-scoped, and they are also packaged as part of the ear. these are not the only artifacts upgraded. this project builds just fine with maven 2. before i start adding a lot of exclusions, what am i missing here ? thanks in advance for any help/ideas/comments/clues, radai.
Request received: maven 3.0.1 pulling in transient dependencies of a provided dependency as compile-scoped (ticket #21943)
## In replies all text above this line is added to the ticket ## Request received: maven 3.0.1 pulling in transient dependencies of a provided dependency as compile-scoped (ticket #21943) Your request (#21943) has been received, and is being reviewed by our support staff. To review the status of the request and add additional comments, follow the link below: http://support.boxee.tv/tickets/21943 -- Maven Users List, Dec-27 06:32 am (EST): i have a maven project that contains the following dependency: dependency groupIdorg.jboss.ejb3/groupId artifactIdjboss-ejb3-core/artifactId version1.6.3/version scopeprovided/scope /dependency this is part of a module that produces an ear artifact. according to the maven dependency scope doc ( http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html) the transient dependencies of a provided-scoped dependency are either scoped as provided or not treated at all. and yet in my case im seeing this as part of the build (produced with -X): [DEBUG] com.emc.illuminator:illuminator-ear:ear:6.0-SNAPSHOT [DEBUG]...some direct dependencies edited out for brevity's sake... [DEBUG]org.jboss.ejb3:jboss-ejb3-core:jar:1.6.3:provided [DEBUG] javassist:javassist:jar:3.7.1.GA:compile [DEBUG] org.hibernate:hibernate-core:jar:3.3.1.GA:provided [DEBUG] antlr:antlr:jar:2.7.6:provided [DEBUG] dom4j:dom4j:jar:1.6.1:compile notice that javassist and dom4j are upgraded to compile-scoped, and they are also packaged as part of the ear. these are not the only artifacts upgraded. this project builds just fine with maven 2. before i start adding a lot of exclusions, what am i missing here ? thanks in advance for any help/ideas/comments/clues, radai. This email is a service from Boxee Support
Re: eclipse : [WARNING] build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing
Do as the messages say, specify the version of those plugins (in the pom). /Anders (mobile) Den 27 dec 2010 10.07 skrev fvo1961 fvo1...@hotmail.com: I've installed m2 Sonatype plugin in eclipse. When I execute package, the following warning messages appear: [WARNING] Some problems were encountered while building the effective model for stockdomain:stockdomain:war:1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 11, column 12 [WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:exec-maven-plugin is missing. @ line 26, column 12 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. Many thanks fo advise on how to get rid of these warning. fv1961 -- View this message in context: http://maven.40175.n5.nabble.com/eclipse-WARNING-build-plugins-plugin-version-for-org-apache-maven-plugins-maven-compiler-plugin-is-mg-tp3318900p3318900.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Request received: Re: eclipse : [WARNING] build.plugins.plugin.version' for org.apache.maven.plugins:maven-comp... (ticket #21944)
## In replies all text above this line is added to the ticket ## Request received: Re: eclipse : [WARNING] build.plugins.plugin.version' for org.apache.maven.plugins:maven-comp... (ticket #21944) Your request (#21944) has been received, and is being reviewed by our support staff. To review the status of the request and add additional comments, follow the link below: http://support.boxee.tv/tickets/21944 -- Maven Users List, Dec-27 07:44 am (EST): Do as the messages say, specify the version of those plugins (in the pom). /Anders (mobile) Den 27 dec 2010 10.07 skrev fvo1961 fvo1...@hotmail.com: I've installed m2 Sonatype plugin in eclipse. When I execute package, the following warning messages appear: [WARNING] Some problems were encountered while building the effective model for stockdomain:stockdomain:war:1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 11, column 12 [WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:exec-maven-plugin is missing. @ line 26, column 12 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. Many thanks fo advise on how to get rid of these warning. fv1961 -- View this message in context: http://maven.40175.n5.nabble.com/eclipse-WARNING-build-plugins-plugin-version-for-org-apache-maven-plugins-maven-compiler-plugin-is-mg-tp3318900p3318900.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This email is a service from Boxee Support
Re: Inline Ant tasks not working - Namespace problem?
I was fighting the same issue trying to get eclemma reports integrated via antrun. Here's a snippet dump that works: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-antrun-plugin/artifactId version1.6/version executions execution phasetest/phase configuration target xmlns:jacoco=antlib:org.jacoco.ant taskdef uri=antlib:org.jacoco.ant resource=org/jacoco/ant/antlib.xml classpath path=/home/lukewpatterson/Desktop/jacocoant.jar / /taskdef jacoco:report executiondata file file=jacoco.exec / /executiondata structure name=Example Project classfiles fileset dir=target/classes / fileset dir=target/test-classes / /classfiles sourcefiles encoding=UTF-8 fileset dir=src/main/groovy / fileset dir=src/test/groovy / /sourcefiles /structure html destdir=target/report / /jacoco:report /target /configuration goals goalrun/goal /goals /execution /executions /plugin obviously I don't have my jacocoant.jar properly GAV'd yet, and have too may hardcoded references, but the important part there is: target xmlns:jacoco=antlib:org.jacoco.ant -- View this message in context: http://maven.40175.n5.nabble.com/Inline-Ant-tasks-not-working-Namespace-problem-tp3246437p3319602.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Request received: Re: Inline Ant tasks not working - Namespace problem? (ticket #21965)
## In replies all text above this line is added to the ticket ## Request received: Re: Inline Ant tasks not working - Namespace problem? (ticket #21965) Your request (#21965) has been received, and is being reviewed by our support staff. To review the status of the request and add additional comments, follow the link below: http://support.boxee.tv/tickets/21965 -- Maven Users List, Dec-27 01:36 pm (EST): I was fighting the same issue trying to get eclemma reports integrated via antrun. Here's a snippet dump that works: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-antrun-plugin/artifactId version1.6/version executions execution phasetest/phase configuration target xmlns:jacoco=antlib:org.jacoco.ant taskdef uri=antlib:org.jacoco.ant resource=org/jacoco/ant/antlib.xml classpath path=/home/lukewpatterson/Desktop/jacocoant.jar / /taskdef jacoco:report executiondata file file=jacoco.exec / /executiondata structure name=Example Project classfiles fileset dir=target/classes / fileset dir=target/test-classes / /classfiles sourcefiles encoding=UTF-8 fileset dir=src/main/groovy / fileset dir=src/test/groovy / /sourcefiles /structure html destdir=target/report / /jacoco:report /target /configuration goals goalrun/goal /goals /execution /executions /plugin obviously I don't have my jacocoant.jar properly GAV'd yet, and have too may hardcoded references, but the important part there is: target xmlns:jacoco=antlib:org.jacoco.ant -- View this message in context: http://maven.40175.n5.nabble.com/Inline-Ant-tasks-not-working-Namespace-problem-tp3246437p3319602.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This email is a service from Boxee Support
Fwd: Maven job in woodlawn maryland
I'm posting this for Rick, who isn't on the list. Just FYI. -K Begin forwarded message: From: Rick Waters rwat...@apexgov.com Date: December 27, 2010 1:37:35 PM CST To: kath...@kathrynhuxtable.org Subject: Maven job in woodlawn maryland Required Qualifications for Apache Maven and Nexus development tools: Start: 1/15/2011 Duration: 1 year Local: must be local resource · Apache Maven SME whose primary work focus is in the implementation of Maven with the Eclipse or RAD development environment, · Technical experience with the installing and customizing Apache Maven, · Technical development or scripting experience integrating with FUSE on Solaris, · Technical experience with Eclipse, RAD, and implementing Maven Plug-ins or customizations in those environments, · Has ability to build Java applications using Maven and can demonstrate key technical concepts using RAD or Eclipse development tools. · Excellent written and verbal communications skills; ability to support software engineering life-cycle (requirements analysis, design alternatives; detail program specifications etc.) Document development may be required · Sonatype Nexus SME whose primary work focus repository development and management to support the implementation of FUSE. · Technical experience with the installing and customizing Sonatype Nexus on Solaris. · Technical development or scripting experience integrating with FUSE on Solaris. · Technical experience with Eclipse, RAD, and implementing Maven Plug-ins or customizations in those environments. · Has ability to build Java applications using RAD or Eclipse and can demonstrate key technical concepts for Nexus repository using the prescribed development development tools. · Excellent written and verbal communications skills; ability to support software engineering life-cycle (requirements analysis, design alternatives; detail program specifications etc.) Document development may be required. Thank You, Rick Waters Director of Resource Management Apex Government Solutions 816-547-1630 rwat...@apexgov.com
Request received: Fwd: Maven job in woodlawn maryland (ticket #21972)
## In replies all text above this line is added to the ticket ## Request received: Fwd: Maven job in woodlawn maryland (ticket #21972) Your request (#21972) has been received, and is being reviewed by our support staff. To review the status of the request and add additional comments, follow the link below: http://support.boxee.tv/tickets/21972 -- Maven Users List, Dec-27 02:44 pm (EST): I'm posting this for Rick, who isn't on the list. Just FYI. -K Begin forwarded message: From: Rick Waters rwat...@apexgov.com Date: December 27, 2010 1:37:35 PM CST To: kath...@kathrynhuxtable.org Subject: Maven job in woodlawn maryland Required Qualifications for Apache Maven and Nexus development tools: Start: 1/15/2011 Duration: 1 year Local: must be local resource · Apache Maven SME whose primary work focus is in the implementation of Maven with the Eclipse or RAD development environment, · Technical experience with the installing and customizing Apache Maven, · Technical development or scripting experience integrating with FUSE on Solaris, · Technical experience with Eclipse, RAD, and implementing Maven Plug-ins or customizations in those environments, · Has ability to build Java applications using Maven and can demonstrate key technical concepts using RAD or Eclipse development tools. · Excellent written and verbal communications skills; ability to support software engineering life-cycle (requirements analysis, design alternatives; detail program specifications etc.) Document development may be required · Sonatype Nexus SME whose primary work focus repository development and management to support the implementation of FUSE. · Technical experience with the installing and customizing Sonatype Nexus on Solaris. · Technical development or scripting experience integrating with FUSE on Solaris. · Technical experience with Eclipse, RAD, and implementing Maven Plug-ins or customizations in those environments. · Has ability to build Java applications using RAD or Eclipse and can demonstrate key technical concepts for Nexus repository using the prescribed development development tools. · Excellent written and verbal communications skills; ability to support software engineering life-cycle (requirements analysis, design alternatives; detail program specifications etc.) Document development may be required. Thank You, Rick Waters Director of Resource Management Apex Government Solutions 816-547-1630 rwat...@apexgov.com This email is a service from Boxee Support
Re: Maven job in woodlawn maryland
I would worry a bit about posting a job for Maven people, but the Boxee thing is quite funny and seems like a more questionable use of the list. ;-) -K On Dec 27, 2010, at 1:44 PM, Kathryn Huxtable wrote: I'm posting this for Rick, who isn't on the list. Just FYI. -K Begin forwarded message: From: Rick Waters rwat...@apexgov.com Date: December 27, 2010 1:37:35 PM CST To: kath...@kathrynhuxtable.org Subject: Maven job in woodlawn maryland Required Qualifications for Apache Maven and Nexus development tools: Start: 1/15/2011 Duration: 1 year Local: must be local resource · Apache Maven SME whose primary work focus is in the implementation of Maven with the Eclipse or RAD development environment, · Technical experience with the installing and customizing Apache Maven, · Technical development or scripting experience integrating with FUSE on Solaris, · Technical experience with Eclipse, RAD, and implementing Maven Plug-ins or customizations in those environments, · Has ability to build Java applications using Maven and can demonstrate key technical concepts using RAD or Eclipse development tools. · Excellent written and verbal communications skills; ability to support software engineering life-cycle (requirements analysis, design alternatives; detail program specifications etc.) Document development may be required · Sonatype Nexus SME whose primary work focus repository development and management to support the implementation of FUSE. · Technical experience with the installing and customizing Sonatype Nexus on Solaris. · Technical development or scripting experience integrating with FUSE on Solaris. · Technical experience with Eclipse, RAD, and implementing Maven Plug-ins or customizations in those environments. · Has ability to build Java applications using RAD or Eclipse and can demonstrate key technical concepts for Nexus repository using the prescribed development development tools. · Excellent written and verbal communications skills; ability to support software engineering life-cycle (requirements analysis, design alternatives; detail program specifications etc.) Document development may be required. Thank You, Rick Waters Director of Resource Management Apex Government Solutions 816-547-1630 rwat...@apexgov.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Tests run twice using assembly plugin
I am using the assembly plugin to build a zip file for a project. This
uses a custom made assembly descriptor.
The pom for this projects lists several modules, each of which has its
own pom and builds a jar.
For some reason I don't understand, this setup causes each submodule to
be attempted to be built twice.
The first time through, each submodule is built and its tests run. The
second time through, maven determines that there is nothing to compile
and doesn't do any building, but the surefire plugin doesn't realize
that there's nothing to do and runs the tests again.
So the root problem appears to be - why is it building everything twice?
That would be the first thing to solve. If this is unavoidable, is
there some way to avoid the tests the second time around?
Thanks
Assembly descriptor:
===
?xml version=1.0 encoding=UTF-8?
assembly
idBPM/id
formats
formatzip/format
/formats
baseDirectorybpm/baseDirectory
moduleSets
moduleSet
binaries
outputDirectorylib/outputDirectory
includeDependencies /
dependencySets
dependencySet
scoperuntime/scope
outputDirectorylib/outputDirectory
useTransitiveDependencies /
/dependencySet
/dependencySets
unpackfalse/unpack
/binaries
/moduleSet
/moduleSets
fileSets
fileSet
directory../Submod1/unpackaged/config/directory
outputDirectoryconfig/outputDirectory
includes
include**/include
/includes
/fileSet
/fileSets
/assembly
POM
===
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/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.what.ever/groupId
artifactIdBPM/artifactId
version0.0.2-SNAPSHOT/version
packagingpom/packaging
nameBPM/name
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-5/version
configuration
descriptorsrc/main/assembly/zip.xml/descriptor
finalName${TAG}/finalName
appendAssemblyIdfalse/appendAssemblyId
/configuration
/plugin
/plugins
/build
dependencies
/dependencies
dependencyManagement
dependencies
/dependencies
/dependencyManagement
modules
module../Submod1/module
module../Submod2/module
module../Submod3/module
/modules
/project
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Request received: Tests run twice using assembly plugin (ticket #21984)
## In replies all text above this line is added to the ticket ##
Request received: Tests run twice using assembly plugin (ticket #21984)
Your request (#21984) has been received, and is being reviewed by our support
staff.
To review the status of the request and add additional comments, follow the
link below:
http://support.boxee.tv/tickets/21984
--
Maven Users List, Dec-27 04:18 pm (EST):
I am using the assembly plugin to build a zip file for a project. This
uses a custom made assembly descriptor.
The pom for this projects lists several modules, each of which has its
own pom and builds a jar.
For some reason I don't understand, this setup causes each submodule to
be attempted to be built twice.
The first time through, each submodule is built and its tests run. The
second time through, maven determines that there is nothing to compile
and doesn't do any building, but the surefire plugin doesn't realize
that there's nothing to do and runs the tests again.
So the root problem appears to be - why is it building everything twice?
That would be the first thing to solve. If this is unavoidable, is
there some way to avoid the tests the second time around?
Thanks
Assembly descriptor:
===
?xml version=1.0 encoding=UTF-8?
assembly
idBPM/id
formats
formatzip/format
/formats
baseDirectorybpm/baseDirectory
moduleSets
moduleSet
binaries
outputDirectorylib/outputDirectory
includeDependencies /
dependencySets
dependencySet
scoperuntime/scope
outputDirectorylib/outputDirectory
useTransitiveDependencies /
/dependencySet
/dependencySets
unpackfalse/unpack
/binaries
/moduleSet
/moduleSets
fileSets
fileSet
directory../Submod1/unpackaged/config/directory
outputDirectoryconfig/outputDirectory
includes
include**/include
/includes
/fileSet
/fileSets
/assembly
POM
===
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/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.what.ever/groupId
artifactIdBPM/artifactId
version0.0.2-SNAPSHOT/version
packagingpom/packaging
nameBPM/name
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-5/version
configuration
descriptorsrc/main/assembly/zip.xml/descriptor
finalName${TAG}/finalName
appendAssemblyIdfalse/appendAssemblyId
/configuration
/plugin
/plugins
/build
dependencies
/dependencies
dependencyManagement
dependencies
/dependencies
/dependencyManagement
modules
module../Submod1/module
module../Submod2/module
module../Submod3/module
/modules
/project
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
This email is a service from Boxee Support
What is this BoxEE support?
Who are they and who gave them the right to create tickets from posts to this list? I had no idea I was working with such an organization. If they are abusing this list, their rights to post here should be revoked. I never saw them until today. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Request received: What is this BoxEE support? (ticket #21989)
## In replies all text above this line is added to the ticket ## Request received: What is this BoxEE support? (ticket #21989) Your request (#21989) has been received, and is being reviewed by our support staff. To review the status of the request and add additional comments, follow the link below: http://support.boxee.tv/tickets/21989 -- Maven Users List, Dec-27 05:38 pm (EST): Who are they and who gave them the right to create tickets from posts to this list? I had no idea I was working with such an organization. If they are abusing this list, their rights to post here should be revoked. I never saw them until today. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This email is a service from Boxee Support
RE: What is this BoxEE support?
-Original Message- From: Steve Cohen [mailto:sco...@javactivity.org] Who are they and who gave them the right to create tickets from posts to this list? I had no idea I was working with such an organization. If they are abusing this list, their rights to post here should be revoked. I never saw them until today. I'll bet someone entered their email when subscribing to the list, and since the boxee address auto-responds, it automatically confirmed itself and now receives, and thus responses to, every single message someone posts to the list. I imagine they'll probably unsubscribe themselves once they get sick of all the tickets in their support system. eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: What is this BoxEE support?
On Mon, Dec 27, 2010 at 5:37 PM, Steve Cohen sco...@javactivity.org wrote: Who are they and who gave them the right to create tickets from posts to this list? I had no idea I was working with such an organization. If they are abusing this list, their rights to post here should be revoked. I never saw them until today. It's most likely not them (Boxee) but someone (or some bot) who thought it would be cute to subscribe their support autoresponder to the list. I asked on the infra irc channel and got it removed. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: What is this BoxEE support?
I'd guess that someone has email from this group forwarded to Boxee support. Either because they hate Boxee, or more likely, as an error somewhere. This may not be the fault of anyone at Boxee. -K On Dec 27, 2010, at 4:37 PM, Steve Cohen wrote: Who are they and who gave them the right to create tickets from posts to this list? I had no idea I was working with such an organization. If they are abusing this list, their rights to post here should be revoked. I never saw them until today. - 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: What is this BoxEE support?
Eric or Wendy are more likely correct than I. -K On Dec 27, 2010, at 5:31 PM, Kathryn Huxtable wrote: I'd guess that someone has email from this group forwarded to Boxee support. Either because they hate Boxee, or more likely, as an error somewhere. This may not be the fault of anyone at Boxee. -K On Dec 27, 2010, at 4:37 PM, Steve Cohen wrote: Who are they and who gave them the right to create tickets from posts to this list? I had no idea I was working with such an organization. If they are abusing this list, their rights to post here should be revoked. I never saw them until today. - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
